Re: Error code=1000

When you say "I am using cassandra standalone", do you mean that you're running a single-node cluster? If that's the case, then I'm guessing your problem is that the replication factor for the keyspace is set to 2 or 3 (instead of 1). On Sat, Oct 31, 2015 at 3:00 PM, Ricardo Sancho wrote: > One

Re: [Ann] Ansible base Cassandra stress framework for EC2

For anyone interested, the framework can now deploy and stress Cassandra on multi EC2 regions. https://github.com/scylladb/cassandra-test-and-deploy Cheers Tzach On Thu, Sep 3, 2015 at 9:21 PM, Tzach Livyatan wrote: > I'm please to share a framework for running Cassandra stress tests on EC2. >

compression cpu overhead

Hey all, Just wondering if anyone has done seen or done any benchmarking for the actual CPU overhead added by various compression algorithms in Cassandra (at least LZ4) vs no compression. Clearly this is going to be workload dependent but even a rough gauge would be helpful (ex. "Turning on LZ4 co

Re: compression cpu overhead

On read or write? https://issues.apache.org/jira/browse/CASSANDRA-7039 and friends in 2.2 should make some difference, I didn’t immediately find perf numbers though. > On Nov 3, 2015, at 5:42 PM, Dan Kinder wrote: > > Hey all, > > Just w

Re: compression cpu overhead

Most concerned about write since that's where most of the cost is, but perf numbers for a any workload mix would be helpful. On Tue, Nov 3, 2015 at 3:48 PM, Graham Sanderson wrote: > On read or write? > > https://issues.apache.org/jira/browse/CASSANDRA-7039 and friends in 2.2 > should make some

Re: Doubt regarding consistency-level in Cassandra-2.1.10

What Eric means is that SERIAL consistency is a special type of consistency that is only invoked for a subset of operations: those that use CAS/lightweight transactions, for example "IF NOT EXISTS" queries. The differences between CAS operations and standard operations are significant and there ar

Re: compression cpu overhead

For writes it's negligible. For reads it makes a significant difference for high tps and low latency workload. You would see up to 3x higher cpu with LZ4 vs no compression. It would be different for different h/w configurations. Thanks, Tushar (Sent from iPhone) > On Nov 3, 2015, at 5:51 PM, D

Re: compression cpu overhead

You won't see any overhead on writes because you don't actually write to sstables when performing a write. Just the commit log & memtable. Memtables are flushes asynchronously. > On Nov 4, 2015, at 1:57 AM, Tushar Agrawal wrote: > > For writes it's negligible. For reads it makes a significan

Re: Doubt regarding consistency-level in Cassandra-2.1.10

Hmm... ok. Ideally, we require :: a) The intra-DC-node-syncing takes place at the statement/query level. b) The inter-DC-node-syncing takes place at cassandra level. That way, we don't spend too much delay at the statement/query level. For the so-called CAS/lightweight transactions, the abov