Add an option that adjusts ZooKeeper fsync warning threshold. #366
Labels
Milestone
Comments
trustin
added a commit
to trustin/centraldogma
that referenced
this issue
Apr 3, 2019
Motivation:
It is usual for fsync to take longer than 1 second in a non-prod
environment, so it'd be nice if we have an option that adjusts the
threshold.
fsync-ing the write ahead log in SyncThread:3 took 1513ms
which will adversely effect operation latency. File size is
67108880 bytes. See the ZooKeeper troubleshooting guide.
Modifications:
- Set the system property `zookeeper.fsync.warningthresholdms` when a
user specified `fsync.warningthresholdms` as an additional property.
Result:
- Closes line#366
trustin
added a commit
that referenced
this issue
Apr 3, 2019
…#377) Motivation: It is usual for fsync to take longer than 1 second in a non-prod environment, so it'd be nice if we have an option that adjusts the threshold. fsync-ing the write ahead log in SyncThread:3 took 1513ms which will adversely effect operation latency. File size is 67108880 bytes. See the ZooKeeper troubleshooting guide. Modifications: - Set the system property `zookeeper.fsync.warningthresholdms` when a user specified `fsync.warningthresholdms` as an additional property. Result: - Closes #366
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is usual for fsync to take longer than 1 second in a non-prod environment, so it'd be nice if we have an option that adjusts the threshold.
The text was updated successfully, but these errors were encountered: