[
https://issues.apache.org/jira/browse/ZOOKEEPER-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084975#comment-16084975
]
ASF GitHub Bot commented on ZOOKEEPER-2770:
-------------------------------------------
Github user tdunning commented on the issue:
https://github.com/apache/zookeeper/pull/307
So here is an alternative suggestion.
For each class of operation (GET, PUT, MULTIPUT, DELETE and so on) maintain
a data structure (such as t-digest or Floathistogram see
https://github.com/tdunning/t-digest) that keeps track of the distribution of
latencies for that operation.
Log any transactions that are above a settable percentile latency for
operations of that class. Default could be 99.99%.
Operations longer than 2x the 99.9%-ile latency should not be entered into
the historical distribution.
> ZooKeeper slow operation log
> ----------------------------
>
> Key: ZOOKEEPER-2770
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2770
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Karan Mehta
> Attachments: ZOOKEEPER-2770.001.patch, ZOOKEEPER-2770.002.patch,
> ZOOKEEPER-2770.003.patch
>
>
> Log the client and request details if the server discovers, when finally
> processing the request, that the current time minus arrival time of the
> request is beyond a configured threshold.
> Look at the HBase {{responseTooSlow}} feature for inspiration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
