[
https://issues.apache.org/jira/browse/HIVE-25793?focusedWorklogId=693665&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-693665
]
ASF GitHub Bot logged work on HIVE-25793:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Dec/21 01:48
Start Date: 10/Dec/21 01:48
Worklog Time Spent: 10m
Work Description: dengzhhu653 edited a comment on pull request #2860:
URL: https://github.com/apache/hive/pull/2860#issuecomment-990517308
The [#2441](https://github.com/apache/hive/pull/2441/files) also wants to
solve the problem, but brings some backwards compatible problem. I am not sure
it appropriate to introduce some more metrics about the apis.
Thanks,
Zhihua Deng
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 693665)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> Remaining Estimate: 0h
>
> We can see that a metastore api count increments twice for one RPC, because a
> metastore server makes two timers with same name for one RPC. one for a
> retrying proxy handler and another for a 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)
