zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3430) Observability improvement: provide top N read / write path queries
Date Thu, 01 Aug 2019 09:17:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897904#comment-16897904
] 

Hudson commented on ZOOKEEPER-3430:
-----------------------------------

FAILURE: Integrated in Jenkins build ZooKeeper-trunk #641 (See [https://builds.apache.org/job/ZooKeeper-trunk/641/])
ZOOKEEPER-3430: Observability improvement: provide top N read / write (eolivelli: rev 6d636025d1c6a10840a27caee9e8933f1dbcbaf0)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/FinalRequestProcessor.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/Request.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (add) zookeeper-server/src/main/java/org/apache/zookeeper/server/util/RequestPathMetricsCollector.java
* (add) zookeeper-server/src/test/java/org/apache/zookeeper/server/util/RequestPathMetricsCollectorTest.java


> 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 40m
>  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)

Mime
View raw message