Thanks Rob
Thanks,
Philo Yang
2014-09-16 2:12 GMT+08:00 DuyHai Doan :
> Nice catch Rob
>
> On Mon, Sep 15, 2014 at 8:04 PM, Robert Coli wrote:
>
>> On Sun, Sep 14, 2014 at 11:22 AM, Philo Yang wrote:
>>
>>> After reading some docs, I find that bloom filter is built on row keys,
>>> not on col
Apologies for the late reply: the 2.1.x version of the C#, Java and Python
DataStax drivers support the new Cassandra 2.1 version.
Here's the quick list of links:
C#:
Latest version: 2.1.2
Nuget: https://www.nuget.org/packages/CassandraCSharpDriver/
Java:
Latest version: 2.1.1
Maven: http://ma
When you say you moved from EBS to SSD, do you mean the EBS HDD drives to
EBS SSD drives? Or instance SSD drives? The m3.large only comes with 32GB
of instance based SSD storage. If you're using EBS SSD drives then network
will still be the slowest thing so switching won't likely make much of a
dif
Hi there,
I am using leveled compaction strategy and have many sstable files. The
error was during the startup, so any idea about this?
> ERROR [FlushWriter:4] 2014-09-17 22:36:59,383 CassandraDaemon.java (line
> 199) Exception in thread Thread[FlushWriter:4,5,main]
> java.lang.OutOfMemoryError:
Are you running on a 32 bit JVM?
On Sep 17, 2014, at 9:43 AM, Yatong Zhang wrote:
> Hi there,
>
> I am using leveled compaction strategy and have many sstable files. The error
> was during the startup, so any idea about this?
>
> ERROR [FlushWriter:4] 2014-09-17 22:36:59,383 CassandraDaemon.
no, I am running 64 bit JVM。 But I have many sstable files, about 30k+
On Wed, Sep 17, 2014 at 10:50 PM, graham sanderson wrote:
> Are you running on a 32 bit JVM?
>
> On Sep 17, 2014, at 9:43 AM, Yatong Zhang wrote:
>
> Hi there,
>
> I am using leveled compaction strategy and have many sstable
sorry, about 300k+
On Wed, Sep 17, 2014 at 10:56 PM, Yatong Zhang wrote:
> no, I am running 64 bit JVM。 But I have many sstable files, about 30k+
>
> On Wed, Sep 17, 2014 at 10:50 PM, graham sanderson
> wrote:
>
>> Are you running on a 32 bit JVM?
>>
>> On Sep 17, 2014, at 9:43 AM, Yatong Zhang
Well, how to upgrade from 2.0.x to 2.1? Just replace cassandra bin files?
On Wed, Sep 17, 2014 at 3:52 PM, Alex Popescu wrote:
> Apologies for the late reply: the 2.1.x version of the C#, Java and Python
> DataStax drivers support the new Cassandra 2.1 version.
>
> Here's the quick list of links
What is your sstable size set to for each of the sstables, using LCS? Are you
at the default of 5 MB?
Rahul Neelakantan
> On Sep 17, 2014, at 10:58 AM, Yatong Zhang wrote:
>
> sorry, about 300k+
>
>> On Wed, Sep 17, 2014 at 10:56 PM, Yatong Zhang wrote:
>> no, I am running 64 bit JVM。 But I
Fixed. Thanks for reporting this!
-- Jack Krupansky
From: ziju feng
Sent: Tuesday, September 16, 2014 8:30 AM
To: user@cassandra.apache.org
Subject: Document of WRITETIME function needs update
Hi,
I found that the WRITETIME function on counter column returns date/time in
milliseconds instead
On Tue, Sep 16, 2014 at 10:00 PM, Mohammed Guller
wrote:
> The 10 seconds latency that I gave earlier is from CQL tracing. Almost 5
> seconds out of that was taken up by the “merge memtable and sstables” step.
> The remaining 5 seconds are from “read live and tombstoned cells.”
>
Could you past
it depends on how you installed it, package vs tar ball etc , Datastax has
good documentation i suggest reading it
http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html
in either case at a high level
Step 1: Stop node
Step 2: Backup your config files
Ste
When I upgraded my system from 1.2.x to 2.0.x there were simple hint:
never upgrade before target release does not have at least 5 on third
place. versions before x.x.5 are unstable and aren't ready for
production use. I don't know if it's still true, but be careful ;)
Regards
Olek
2014-09-17 20:1
I'm using the Cassandra 2.0.9 with JAVA datastax driver.
I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
operation.
I have a Column family filled with some keys (for example 'a' and 'b').
When this keys are deleted and inserted hereafter, sporadically this keys
disappear.
On Wed, Sep 17, 2014 at 11:55 AM, Sávio S. Teles de Oliveira <
savio.te...@cuia.com.br> wrote:
> I'm using the Cassandra 2.0.9 with JAVA datastax driver.
> I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
> operation.
>
> I have a Column family filled with some keys (for e
Make sure your clocks are synced. If they aren't, the writetime that
determines the most recent value will be incorrect.
On Wed, Sep 17, 2014 at 11:58 AM, Robert Coli wrote:
> On Wed, Sep 17, 2014 at 11:55 AM, Sávio S. Teles de Oliveira
> wrote:
>>
>> I'm using the Cassandra 2.0.9 with JAVA dat
Could you be experiencing
https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
On Wed, Sep 17, 2014 at 2:09 PM, Jonathan Haddad wrote:
> Make sure your clocks are synced. If they aren't, the writetime that
> determines the most recent value will be incorrect.
>
> On Wed, Sep 17, 2014 at 11:58
The clocks are synced.
Could you be experiencing
> https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
Yes, its similar Philip. How can I solve this problem?
2014-09-17 16:16 GMT-03:00 Philip Thompson :
> Could you be experiencing
> https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
>
>
Philip, I'm not using "IF NOT EXISTS" on insert command.
2014-09-17 16:51 GMT-03:00 Sávio S. Teles de Oliveira <
savio.te...@cuia.com.br>:
> The clocks are synced.
>
> Could you be experiencing
>> https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
>
>
> Yes, its similar Philip. How can I solv
I have recently started working with Cassandra. We have cassandra cluster
which is using DSE 4.0 version and has VNODES enabled. We have a tables
like this -
Below is my first table -
CREATE TABLE customers (
customer_id int PRIMARY KEY,
last_modified_date timeuuid,
customer
On 17 Sep 2014, at 20:55, Sávio S. Teles de Oliveira
wrote:
> I'm using the Cassandra 2.0.9 with JAVA datastax driver.
> I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
> operation.
>
> I have a Column family filled with some keys (for example 'a' and 'b').
> When th
Perhaps you're seeing this:
https://issues.apache.org/jira/browse/CASSANDRA-6178
TL;DR: rapid deletes and inserts of the same key may use the same
timestamp, in which case the delete wins. Specifying the timestamp
explicitly in the CQL query is a good workaround. Alternatively, other
drivers whi
When I upgraded I went from scripts to create tables and load data then tested
on a clean server (no previous install of Cassandra). So far things are running
well for me. I discovered else Cassandra will look for previous installs and if
you do not follow the Cassandra's team recommendation you
Thanks Rob for pointing me to that link. I haven't gone through all the
JIRAs but I guess it talks about adv & disadv of Secondary Index in
Cassandra which I understand by now but doesn't really talk about why the
default implementation of Secondary Index didn't take the DSE/Solr approach?
Hi Jack
Just upgraded cassandra to 2.1 on my own box and when I try to connect to
our server running 2.0.7, I get the following error.
Connection error: ('Unable to connect to any servers', {'10.0.16.144':
ConnectionShutdown('Connection is already closed',)})
With debug on I get the following output.
U
This is not really supported. Presently cqlsh hard-codes CQL and protocol
to versions only supported in 2.1:
https://github.com/apache/cassandra/blob/cassandra-2.1.0/bin/cqlsh#L144-L147
Your best bet is probably downloading a 2.0.x tarball and running out of
there.
Adam Holmberg
On Wed, Sep 17,
Thank you all for your responses.
Alex –
Instance (ephemeral) SSD
Ben –
the query reads data from just one partition. If disk i/o is the bottleneck,
then in theory, if reading from EBS takes 10 seconds, then it should take lot
less when reading the same amount of data from local SSD. My quest
How slow is slow? Regardless of the data model question, in my experience
500 rows of relatively light content should be lightning fast. Looking at
my performance results on a test cluster of 3x r3.large AWS instances, we
reach an op rate on Cassandra's stress test of at least 1000 operations per
s
It takes around more than 50 seconds to return back 500 records from cqlsh
command not from the code so that's why I am saying it is pretty slow.
On Wed, Sep 17, 2014 at 3:17 PM, Hao Cheng wrote:
> How slow is slow? Regardless of the data model question, in my experience
> 500 rows of relatively
My sstable size is 192MB. I removed some data directories to reduce the
data that need to load, and this time it worked, so I was sure this was
because of the data was too large.
I tried to tune the JVM parameters, like heap size or stack size, but
didn't help. I finally got it resolved by add some
@Chris Lohfink I have 16G memory per node, all the other settings are
default
@J. Ryan Earl I am not sure. I am using the default settings.
But I've found out it might be because some settings in '/etc/sysctl.conf'.
I am still testing it
On Wed, Sep 17, 2014 at 11:46 AM, J. Ryan Earl wrote:
>
Can you post the output of "free" before starting cassandra? Is there anything
in logs before it runs out of memory (ie in /var/log/cassandra/output.log)? If
an exception is thrown with an OOM it might narrow down if theres a kernel
resource (ie mmap file limit, file descriptor limit etc) that y
Check out that the limits here are set correctly:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRecommendSettings.html
particularly the:
* mmap limit which is really what this looks like...
* nproc limit which on some distros defaults to 1024 can be your issue
(ma
"Read 193311 live and 0 tombstoned cells "
is your killer. returning 250k rows is a bit excessive, you should really page
this in smaller chunks, what client are you using to access the data? This
partition (a, b, c, d, e, f) may be too large as well (can check partition max
size from output
Stratio and Stargate are at the Lucene level – DSE/Solr is at the Solr level.
DSE/Solr supports both inserts and queries from either Cassandra or Solr – a
Solr server is running on each Cassandra node that indexes and queries the data
on that node.
DSE/Solr does have CQL SELECT integration as w
Chris,
I agree that reading 250k row is a bit excessive and that breaking up the
partition would help reduce the query time. That part is well understood. The
part that we can't figure out is why read time did not change when we switched
from a slow Network Attached Storage (AWS EBS) to local SS
36 matches
Mail list logo
