You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2023/08/16 13:29:00 UTC

[jira] [Commented] (HBASE-28026) DefaultMetricsSystemInitializer should be called during HMaster or HRegionServer creation

    [ https://issues.apache.org/jira/browse/HBASE-28026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755056#comment-17755056 ] 

Duo Zhang commented on HBASE-28026:
-----------------------------------

Thanks for putting this up!

> 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
>            Assignee: 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 during HMaster/RS process creation. We may need to refactor/move the code around to fix the same.
> See review comments of [https://github.com/apache/hbase/pull/5323] for more details.
> CC: [~zhangduo] 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)