> I current have 3 nodes cluster running with a replication factor of 1. That is a very strange setup.
> Actually I'm noticing that my commit log size is always very big How big? The commitlog_total_space_in_mb setting in the yaml file controls the maximum size. note that these files are pre-allocated and are recycled. > 1- When a commit log gets bigger, does it mean that cassandra hasnt processed > yet those writes? No. They are written to the commit log, added to memory and then flushed to disk when need. > 2- How could I speed my flushes to sstables? Do you need to? > 3- Does my commit log decrease as much as my sstable increases? Is it a rule? No. The commit log is all writes, the memtables and the sstables are the "latest" writes for the columns. Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 24/01/2013, at 4:48 AM, Víctor Hugo Oliveira Molinar <vhmoli...@gmail.com> wrote: > Hi fellows. > I current have 3 nodes cluster running with a replication factor of 1. > It's a pretty simple deployment and all my enforcements are focused in writes > rather than reads. > Actually I'm noticing that my commit log size is always very big if compared > to the ammout of data being persisted(which varies on 5gb). > > So, that lead me to three doubts: > 1- When a commit log gets bigger, does it mean that cassandra hasnt processed > yet those writes? > 2- How could I speed my flushes to sstables? > 3- Does my commit log decrease as much as my sstable increases? Is it a rule?
