[GitHub] zookeeper issue #566: ZOOKEEPER-3062: mention fsync.warningthresholdms in Fi...

2018-08-01 Thread phunt
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/566 lgtm. +1, thanks @cpoerschke . Perhaps consider logging the value during startup (initial read of the value) instead? ---

[GitHub] zookeeper issue #566: ZOOKEEPER-3062: mention fsync.warningthresholdms in Fi...

2018-07-27 Thread cpoerschke
Github user cpoerschke commented on the issue: https://github.com/apache/zookeeper/pull/566 Thanks everyone for your feedback! > ... are you ok with removing the extra words in the log message? Hmm, ok, done. Should I update the pull request and

[GitHub] zookeeper issue #566: ZOOKEEPER-3062: mention fsync.warningthresholdms in Fi...

2018-07-26 Thread breed
Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/566 i agree with @maoling, logging it with every warning seems overkill. the rest of the change looks great though. are you ok with removing the extra words in the log message? ---

[GitHub] zookeeper issue #566: ZOOKEEPER-3062: mention fsync.warningthresholdms in Fi...

2018-07-17 Thread maoling
Github user maoling commented on the issue: https://github.com/apache/zookeeper/pull/566 Is is really necessary to log this property `fsync.warningthresholdms`? ---