If you had Cassandra 2.0.x (possibly before) and upgraded to Cassandra 2.1, you
may have had
commitlog_sync: batch
commitlog_sync_batch_window_in_ms: 25
in you cassiandra.yaml
It turned out that this was pretty much broken in 2.0 (i.e. fsyncs just
happened immediately), but fixed in 2.1,
On 10/19/2015 10:55 AM, Graham Sanderson wrote:
If you had Cassandra 2.0.x (possibly before) and upgraded to Cassandra
2.1, you may have had
commitlog_sync: batch
commitlog_sync_batch_window_in_ms: 25
in you cassiandra.yaml
It turned out that this was pretty much broken in 2.0 (i.e. fsyncs
But basically if you were on 2.1.0 thru 2.1.5 you probably couldn’t know to
change your config
If you were on 2.1.6 thru 2.1.8 you may not have noticed the NEWS.TXT change
and changed your config
If you are on 2.1.9+ you are probably OK
if you are using periodic fsync then you don’t have an
- commitlog_sync_batch_window_in_ms behavior has changed from the
maximum time to wait between fsync to the minimum time. We are
working on making this more user-friendly (see CASSANDRA-9533) but in the
meantime, this means 2.1 needs a much smaller batch window to keep
writer threads
