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

Christine Poerschke commented on ZOOKEEPER-3062:
------------------------------------------------

bq. ... Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1926//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 ...

https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1926/artifact/build/test/findbugs/newPatchFindbugsWarnings.html
 looks to be the correct url -- checking.

> 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
>              Labels: pull-request-available
>         Attachments: ZOOKEEPER-3062.patch, ZOOKEEPER-3062.patch
>
>          Time Spent: 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)

Reply via email to