[
https://issues.apache.org/jira/browse/HBASE-27617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693612#comment-17693612
]
tianhang tang commented on HBASE-27617:
---------------------------------------
Hi [~bbeaudreault], thanks for your reviewing!
You know I also think this solution is a little tricky. After our discussion,
especially after roughly reading relevant code, I tend to think your idea is
more appropriate, there is no need to add a piece of code that is destined to
be removed for a minor issue.
So if you don't mind, I wish I can close this PR, create an issue and directly
start the refactoring work we mentioned above.
Thank you.
> Make metrics from MetricsTableLatenciesImpl removable
> -----------------------------------------------------
>
> Key: HBASE-27617
> URL: https://issues.apache.org/jira/browse/HBASE-27617
> Project: HBase
> Issue Type: Bug
> Reporter: tianhang tang
> Assignee: tianhang tang
> Priority: Major
>
> Now the table latency metrics will last forever on a RS.
> Could reproduce this issue easily:
> 1. Create a test table and the region opened on RS_A;
> 2. Do a query;
> 3. Move the table to another group;
> 4. See JMX on RS_A, table latency metrics still exists and will not deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
