zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-3560) Add response cache to serve get children (2) requests.
Date Thu, 26 Sep 2019 06:35:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ASF GitHub Bot updated ZOOKEEPER-3560:
--------------------------------------
    Labels: pull-request-available  (was: )

> Add response cache to serve get children (2) requests.
> ------------------------------------------------------
>
>                 Key: ZOOKEEPER-3560
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3560
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Michael Han
>            Assignee: Michael Han
>            Priority: Major
>              Labels: pull-request-available
>
> ZOOKEEPER-3180 introduces response cache but it only covers getData requests. This JIRA
is to extend the response cache based on the infrastructure set up by ZOOKEEPER-3180 to so
the response of get children requests can also be served out of cache. Some design decisions:
> * Only OpCode.getChildren2 is supported, as OpCode.getChildren does not have associated
stats and current cache infra relies on stats to invalidate cache.
> * The children list is stored in a separate response cache object so it does not pollute
the existing data cache that's serving getData requests, and this separation also allows potential
separate tuning of each cache based on workload characteristics.
> * As a result of cache object separation, new server metrics is added to measure cache
hit / miss for get children requests, that's separated from get data requests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message