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?



--
View this message in context: 
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Large-commit-log-reasons-tp7584964.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at 
Nabble.com.

Reply via email to