You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Ogasawara (JIRA)" <ji...@apache.org> on 2016/03/04 22:47:40 UTC

[jira] [Created] (CASSANDRA-11307) Inappropriate WARN log message for commit log sync delay when using commitlog_sync: batch

Gary Ogasawara created CASSANDRA-11307:
------------------------------------------

             Summary: Inappropriate WARN log message for commit log sync delay when using commitlog_sync: batch
                 Key: CASSANDRA-11307
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11307
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Linux
            Reporter: Gary Ogasawara
            Priority: Minor


In v2.1.11 when using configuration
commitlog_sync: batch
commitlog_sync_batch_window_in_ms: 2

will frequently get this WARN log though there is not a real problem.

WARN  [COMMIT-LOG-WRITER] 2016-03-03 00:40:11,646 AbstractCommitLogService.java:105 - Out of 142412 commit log syncs over the past 300s with average duration of 0.00ms, 35 have exceeded the configured commit interval by an average of 3.66ms

WARN  [COMMIT-LOG-WRITER] 2016-03-03 00:45:11,755 AbstractCommitLogService.java:105 - Out of 104605 commit log syncs over the past 300s with average duration of 1.74ms, 18314 have exceeded the configured commit interval by an average of 6.33ms

Looks like BatchCommitLogService sets AbstractCommitLogService() pollIntervalMillis to the configured commitlog_sync_batch_window_in_ms.  Since CASSANDRA-9504, this is by default set to 2 which causes this WARN message to be triggered unnecessarily.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)