[
https://issues.apache.org/jira/browse/HBASE-28026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain updated HBASE-28026:
-------------------------------
Description:
Concern is the jvm metrics somehow started populating with process name as IO
instead of expected RegionServer/Master. See
https://issues.apache.org/jira/browse/HBASE-27966 for RCA and a stop-gap fix.
But this does not fix the problem, just hides it, we should be able to figure
out why the metrics is getting initialized in BaseSourceImpl instead of
See review comments of [https://github.com/apache/hbase/pull/5323] for details
was:
See review comments of [https://github.com/apache/hbase/pull/5323] for details
Also see https://issues.apache.org/jira/browse/HBASE-27966 for RCA
> DefaultMetricsSystemInitializer should be called during HMaster or
> HRegionServer creation
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-28026
> URL: https://issues.apache.org/jira/browse/HBASE-28026
> Project: HBase
> Issue Type: Bug
> Components: metrics
> Reporter: Nihal Jain
> Priority: Major
>
> Concern is the jvm metrics somehow started populating with process name as IO
> instead of expected RegionServer/Master. See
> https://issues.apache.org/jira/browse/HBASE-27966 for RCA and a stop-gap fix.
> But this does not fix the problem, just hides it, we should be able to figure
> out why the metrics is getting initialized in BaseSourceImpl instead of
> See review comments of [https://github.com/apache/hbase/pull/5323] for details
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
