[
https://issues.apache.org/jira/browse/PHOENIX-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877222#comment-17877222
]
Viraj Jasani commented on PHOENIX-7395:
---------------------------------------
For client side metadata cache, we have cache hit and miss counter, so we can
add remaining (used cache size and cache eviction rate) whereas for server side
metadata cache, we should add all of above mentioned metrics.
> Metadata Cache metrics at server and client side
> ------------------------------------------------
>
> Key: PHOENIX-7395
> URL: https://issues.apache.org/jira/browse/PHOENIX-7395
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: Viraj Jasani
> Priority: Major
>
> Phoenix maintains cache of PTable objects, also known as Metadata cache (as a
> Guava cache) at both server and client side. The size of the cache at server
> side is determined by config _phoenix.coprocessor.maxMetaDataCacheSize_ with
> default value of 20 MB. Similarly, the size of the cache at client side is
> determined by _phoenix.client.maxMetaDataCacheSize_ with default value of 10
> MB.
> To understand whether the size of the metadata caches at client and server
> side are sufficient for the given cluster and the give client, we need some
> visibility into how efficiently the caches are being utilized.
> The purpose of this Jira is to add some metrics for both of these caches:
> * Used cache size (in bytes)
> * Cache hit rates (per second)
> * Cache miss rates (per second)
> * Cache eviction rates (per second)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
