[
https://issues.apache.org/jira/browse/ZOOKEEPER-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved ZOOKEEPER-3430.
----------------------------------------
Resolution: Fixed
Fix Version/s: 3.6.0
Issue resolved by pull request 989
[https://github.com/apache/zookeeper/pull/989]
> Observability improvement: provide top N read / write path queries
> ------------------------------------------------------------------
>
> Key: ZOOKEEPER-3430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3430
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.6.0
> Reporter: Michael Han
> Assignee: Michael Han
> Priority: Major
> Labels: Twitter, pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> We would like to have a better understanding of the type of workloads hit ZK,
> and one aspect of such understanding is to be able to answer queries of top N
> read and top N write request path. Knowing the hot request paths will allow
> us better optimize for such workloads, for example, enabling path specific
> caching, or change the path structure (e.g. break a long path to hierarchical
> paths).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
