Re: High-read latency for non-existing rows with LCS and 1.2.5

> We are using Leveled Compaction with Cassandra 1.2.5. Our sstable size is > 100M. On each node, > we have anywhere from 700+ to 800+ sstables (for all levels). The > bloom_filter_fp_chance is set at 0.000744. The current default bloom_filter_fp_chance is 0.1 for levelled compaction. Reducing t

RE: Problem using sstableloader with SSTableSimpleUnsortedWriter and a composite key

Thank you Aaaron! Your blog post helped me understand how a row with a compound key is stored and this helped me understand how to create the sstable files. For anyone who needs it this is how it works: In Cassandra-cli the row looks like this: RowKey: 5 => (column=10:created, value=013f84be

Patterns for enabling Compute apps which only request Local Node's

Data Reply-To: Hello Cassandra-user ml, how is everyone? Question; if we're co-locating our Cassandra and our compute application on the same nodes, are there any in-use patterns in Cassandra user (or Cassandra dev) applications for having the compute application only pull data off the localh

Re: Cassandra terminates with OutOfMemory (OOM) error

Yes, it is one read request. Since Cassandra does not support GROUP BY, I was trying to implement it in our application. Hence the need to read large amount of data. I guess that was a bad idea. Mohammed On Jun 27, 2013, at 9:54 PM, "aaron morton" mailto:aa...@thelastpickle.com>> wrote: If

Re: Errors while upgrading from 1.1.10 version to 1.2.4 version

Thanks for the pointer Fabien. From: Fabien Rousseau mailto:fab...@yakaz.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Date: Friday, June 28, 2013 6:35 PM To: "user@cassandra.apache.org" mailto:

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

These two fields: CompressedRandomAccessReader.buffer CompressedRandomAccessReader.compressed in the queue SSTableReader.dfile.pool consumed those memory. I think the SSTableReader.dfile is the cache of the SSTable file. On Sat, Jun 29, 2013 at 1:09 PM, aaron morton wrote: > Lots of memory are