Why shouldn't we worry the warning if it is on its own. I am seeing such warnings frequently in my logs.
WARN [PERIODIC-COMMIT-LOG-SYNCER] 2020-07-07 12:02:56,536 AbstractCommitLogService.java:105 - Out of 179 commit log syncs over the past 302s with average duration of 1282.88ms, 1 have exceeded the configured commit interval by an average of 1.00ms
The PERIODIC-COMMIT-LOG-SYNCER is a service that fulfils the contract of syncing the commit logs (with fsync) to disk based on these settings in cassandra.yaml:
commitlog_sync: periodic commitlog_sync_period_in_ms: 10000
Warning messages (such as the one you posted) in the Cassandra logs indicate that the interval between fsync calls took longer that the sync period.
The warnings in earlier versions of Cassandra are false alarms. There was a bug in the way the sync interval was getting calculated in AbstractCommitLogService.java leading to warnings logged incorrectly (CASSANDRA-14451).
The bug was fixed in Cassandra 3.0.17 and 3.11.3. Upgrade to the latest version to take advantage of improvements and fixes.
In your case, the log entry by the AbstractCommitLogService is from line 105:
WARN [PERIODIC-COMMIT-LOG-SYNCER] ... AbstractCommitLogService.java:105 ...
This indicates that your cluster is running a very old version of Cassandra, most likely version 2.1.21 (or older). In which case, it isn't soo relevant unless you're seeing dropped mutations as well which means the commitlog disk cannot keep up with the writes. When the commitlog disk is overloaded with IO traffic, it can cause the syncs to fall behind. Cheers!
5 People are following this question.
