It looks like you're trying to use batches as a performance
optimization. Don't do that, it makes your load bursty.
On Sat, Oct 8, 2011 at 7:13 PM, Philippe wrote:
> Dear all,
> I've just fired up our production cluster : 12 nodes, RF=3 and I've run into
> something I don't understand at all. Our
The difference is that the Batch executor guarantees that sync will be
called before a task is marked done.
2011/10/8 hicks :
> hi,all:
> i have a question about the option "commitlog_sync" in cassandra.yaml
> file.when its value is set to "batch",the ICommitLogExecutorService instance
> of Comm
Hi,
here is some further information. Compaction did not help, but data is
still there when I dump the row with sstable2json.
Best,
Thomas
On 10/08/2011 11:30 PM, Thomas Richter wrote:
> Hi,
>
> we are running a 3 node cassandra (0.7.6-2) cluster and some of our
> column families contain quite
Hi
at highest traffic hours i get 54 memtable flushes, this happens for a few
hours during the day and at the rest of hours its ranging from 0 to 10 .
Should I be doing anything about it? is that number on critical level? can i
live with 54 memtable flushes per hour during peak hours? (I might ex
Dne 7.10.2011 23:16, Mohit Anchlia napsal(a):
You'll see output like:
Offset SSTables
1 8021
2 783
Which means 783 read operations accessed 2 SSTables
thank you for explaining it to me. I see this:
Offset SSTables
1 59323
2
