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
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.
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.
1. The commit log is only read on startup.
W: If writes are unflushed then the commit logs need to be replayed
2: shrink the memtable settings.
but you dont want to do this.
3. Commit log size is not directly related to sstable size.
E.g. if you write the same row a billion times the commit log
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
