You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Christine Poerschke (JIRA)" <ji...@apache.org> on 2018/06/13 13:48:00 UTC

[jira] [Updated] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christine Poerschke updated ZOOKEEPER-3062:
-------------------------------------------
    Attachment: ZOOKEEPER-3062.patch

> mention fsync.warningthresholdms in FileTxnLog LOG.warn message
> ---------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3062
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3062
>             Project: ZooKeeper
>          Issue Type: Task
>            Reporter: Christine Poerschke
>            Priority: Minor
>         Attachments: ZOOKEEPER-3062.patch
>
>
> The
> {code}
> fsync-ing the write ahead log in ... took ... ms which will adversely effect operation latency. File size is ... bytes. See the ZooKeeper troubleshooting guide
> {code}
> warning mentioning the {{fsync.warningthresholdms}} configurable property would make it easier to discover and also when interpreting historical vs. current logs or logs from different ensembles then differences in configuration would be easier to spot.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)