[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-3062: ------------------------------------ Fix Version/s: 3.4.14 3.5.5 3.6.0 > 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 > Affects Versions: 3.5.4, 3.6.0, 3.4.13 > Reporter: Christine Poerschke > Assignee: Christine Poerschke > Priority: Minor > Labels: pull-request-available > Fix For: 3.6.0, 3.5.5, 3.4.14 > > Attachments: ZOOKEEPER-3062.patch, ZOOKEEPER-3062.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > 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)