[
https://issues.apache.org/jira/browse/HIVE-25793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeongdae Kim updated HIVE-25793:
--------------------------------
Description:
We can see that metastore api count increments twice for one RPC, because a
metastore server makes two timers with same name for one RPC. one for retrying
proxy handler and another for hms handler. It will make api metrics more
inaccurate, especially during retrying.
I think new metrics for retrying proxy will be helpful to make each metric
accurate.
was:A metastore proxy for retrying (RetryingHMSHandler) and a base handler
(HMSHandler) uses the same name for metrics. it makes metastore metrics
inaccurate. ex) rpc counts increment twice for a rpc.
> Isolate metastore metrics related to a retrying handler
> -------------------------------------------------------
>
> Key: HIVE-25793
> URL: https://issues.apache.org/jira/browse/HIVE-25793
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.3.8, 3.1.2, 4.0.0
> Reporter: Jeongdae Kim
> Assignee: Jeongdae Kim
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can see that metastore api count increments twice for one RPC, because a
> metastore server makes two timers with same name for one RPC. one for
> retrying proxy handler and another for hms handler. It will make api metrics
> more inaccurate, especially during retrying.
> I think new metrics for retrying proxy will be helpful to make each metric
> accurate.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
