zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message
Date Wed, 13 Jun 2018 19:41:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511584#comment-16511584

Andor Molnar commented on ZOOKEEPER-3062:


Isn't this property exposed via JMX / Jetty / 4LWs?

Do we really need to add it to every single warning message?

Testing side:

Please remove unit test to verify constant values. It doesn't make any sense to me.

> 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

View raw message