GitHub user karanmehta93 reopened a pull request:
https://github.com/apache/zookeeper/pull/307
ZOOKEEPER-2770 ZooKeeper slow operation log
ZooKeeper is a complex distributed application. There are many reasons why
any given read or write operation may become slow: a software bug, a protocol
problem, a hardware issue with the commit log(s), a network issue. If the
problem is constant it is trivial to come to an understanding of the cause.
However in order to diagnose intermittent problems we often don't know where,
or when, to begin looking. We need some sort of timestamped indication of the
problem. Although ZooKeeper is not a datastore, it does persist data, and can
suffer intermittent performance degradation, and should consider implementing a
'slow query' log, a feature very common to services which persist information
on behalf of clients which may be sensitive to latency while waiting for
confirmation of successful persistence.
The patch sets a default threshold of 10 sec for request. If the value of
warn.responseTime is configured as -1 then logging is ignored.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karanmehta93/zookeeper ZOOKEEPER-2770
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/307.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #307
----
commit bf0ed9eca106faebca6548122108e3ff123b04d3
Author: Karan Mehta <[email protected]>
Date: 2017-10-26T01:48:56Z
ZOOKEEPER-2770 ZooKeeper slow operation log
----
---
