I recently started using Cassandra 1.0.4 and observed that it takes a lot
longer to flush the commit logs to SSTables, than was observed in versions
0.7.X and 0.8.X under constant load conditions with commitlog_sync as
periodic and commitlog_sync_period_in_ms as 10000. As more data gets
retained in commit logs, if a node goes down, it will take longer for
commitlog replay. I am wondering about the configuration options in 1.0
that are related to commit log and memtable flushing. What are the settings
that help flush memtables more frequently or less frequently under constant
load conditions?

Would appreciate any help on this subject.

Reply via email to