[ 
https://issues.apache.org/jira/browse/HBASE-30473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junegunn Choi updated HBASE-30473:
----------------------------------
    Release Note: 
Adds nine numeric gauges for Master switch states: balancerEnabled, 
normalizerEnabled, splitEnabled, mergeEnabled, cleanerChoreEnabled, 
catalogJanitorEnabled, snapshotCleanupEnabled, 
replicationPeerModificationEnabled, and rpcThrottleEnabled.

The gauges are exposed by the active, initialized Master under 
Hadoop:service=HBase,name=Master,sub=Server. Values are 1 for enabled and 0 for 
disabled.

> Expose Master switch states as numeric metrics
> ----------------------------------------------
>
>                 Key: HBASE-30473
>                 URL: https://issues.apache.org/jira/browse/HBASE-30473
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, metrics
>            Reporter: Junegunn Choi
>            Assignee: Junegunn Choi
>            Priority: Minor
>              Labels: pull-request-available
>
> h2. Problem
> Operators can disable cluster-wide services through HBase shell switches, but 
> most switch states are not exported as metrics. For example, 
> {{cleaner_chore_switch false}} disables HFile and WAL cleaning, and operators 
> must run {{cleaner_chore_enabled}} to check that state. A monitoring system 
> cannot directly detect that the cleaner was left disabled. (Only the balancer 
> exports {{tag.isBalancerActive}} as a string tag in a separate metrics 
> source.)
> h2. Proposed Fix
> Expose nine numeric gauges under 
> {{Hadoop:service=HBase,name=Master,sub=Server}}:
> - {{balancerEnabled}}
> - {{normalizerEnabled}}
> - {{splitEnabled}}
> - {{mergeEnabled}}
> - {{cleanerChoreEnabled}}
> - {{catalogJanitorEnabled}}
> - {{snapshotCleanupEnabled}}
> - {{replicationPeerModificationEnabled}}
> - {{rpcThrottleEnabled}}
> Use {{1}} for enabled and {{0}} for disabled. {{rpcThrottleEnabled}} reports 
> {{-1}} when quota support is enabled but the quota manager is not ready.



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

Reply via email to