thangTang commented on PR #5012: URL: https://github.com/apache/hbase/pull/5012#issuecomment-1428990373
> Is this solving an actual problem? It's hard to imagine this "leak" causing any issue unless a cluster has way more tables than is practical for other reasons, but maybe I'm missing something. Yes it's for real problem. For example, group_a has a RS called rs_a and a table called table_a. After we move table_a to another group, the latency metrics of table_a still exist on rs_a, and we have no way to clear it unless restart rs. For monitor dashboard, this creates confusion. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
