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

Umesh Kumar Kumawat updated HBASE-23996:
----------------------------------------
    Description: 
Many split related metrics were present RS side but after split is moved to 
Master, these metrics are lost.

Many of the split related metrics like following are present RS side :

"SplitTime_num_ops": 0,
"SplitTime_min": 0,
"SplitTime_max": 0,
"SplitTime_mean": 0,
"SplitTime_25th_percentile": 0,
"SplitTime_median": 0,
"SplitTime_75th_percentile": 0,
"SplitTime_90th_percentile": 0,
"SplitTime_95th_percentile": 0,
"SplitTime_98th_percentile": 0,
"SplitTime_99th_percentile": 0,
"SplitTime_99.9th_percentile": 0,

Value of these will always be 0 since Split is happening Master side and there 
is no Metrics update. 

 

 

Update 1: After the fix, JMX is like this :

{ "name": "Hadoop:service=HBase,name=Master,sub=Procedure", "modelerType": 
"Master,sub=Procedure", "tag.Context": "master", "tag.Hostname": 
"blrphispra01257", "numMasterWALs": 0, "splitProcedure_RequestCount": 0, 
"splitProcedure_FailedCount": 0, "splitProcedure_SuccessCount": 0, 
"splitProcedureTime_num_ops": 0, "splitProcedureTime_min": 0, 
"splitProcedureTime_max": 0, "splitProcedureTime_mean": 0, 
"splitProcedureTime_25th_percentile": 0, "splitProcedureTime_median": 0, 
"splitProcedureTime_75th_percentile": 0, "splitProcedureTime_90th_percentile": 
0, "splitProcedureTime_95th_percentile": 0, 
"splitProcedureTime_98th_percentile": 0, "splitProcedureTime_99th_percentile": 
0, "splitProcedureTime_99.9th_percentile": 0 }

,

 

,

  was:
Many of the split related metrics like following are present RS side :

"SplitTime_num_ops": 0,
 "SplitTime_min": 0,
 "SplitTime_max": 0,
 "SplitTime_mean": 0,
 "SplitTime_25th_percentile": 0,
 "SplitTime_median": 0,
 "SplitTime_75th_percentile": 0,
 "SplitTime_90th_percentile": 0,
 "SplitTime_95th_percentile": 0,
 "SplitTime_98th_percentile": 0,
 "SplitTime_99th_percentile": 0,
 "SplitTime_99.9th_percentile": 0,

Value of these will always be 0 since Split is happening Master side and there 
is no Metrics update. 

 

 

Update 1: After the fix, JMX is like this :

{
 "name": "Hadoop:service=HBase,name=Master,sub=Procedure",
 "modelerType": "Master,sub=Procedure",
 "tag.Context": "master",
 "tag.Hostname": "blrphispra01257",
 "numMasterWALs": 0,
 "splitProcedure_RequestCount": 0,
 "splitProcedure_FailedCount": 0,
 "splitProcedure_SuccessCount": 0,
 "splitProcedureTime_num_ops": 0,
 "splitProcedureTime_min": 0,
 "splitProcedureTime_max": 0,
 "splitProcedureTime_mean": 0,
 "splitProcedureTime_25th_percentile": 0,
 "splitProcedureTime_median": 0,
 "splitProcedureTime_75th_percentile": 0,
 "splitProcedureTime_90th_percentile": 0,
 "splitProcedureTime_95th_percentile": 0,
 "splitProcedureTime_98th_percentile": 0,
 "splitProcedureTime_99th_percentile": 0,
 "splitProcedureTime_99.9th_percentile": 0
 },

 

,


> Add metric for the split WAL procedure
> --------------------------------------
>
>                 Key: HBASE-23996
>                 URL: https://issues.apache.org/jira/browse/HBASE-23996
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 2.2.3
>            Reporter: Sanjeet Nishad
>            Assignee: Sanjeet Nishad
>            Priority: Minor
>         Attachments: HBASE-23996.001.patch
>
>
> Many split related metrics were present RS side but after split is moved to 
> Master, these metrics are lost.
> Many of the split related metrics like following are present RS side :
> "SplitTime_num_ops": 0,
> "SplitTime_min": 0,
> "SplitTime_max": 0,
> "SplitTime_mean": 0,
> "SplitTime_25th_percentile": 0,
> "SplitTime_median": 0,
> "SplitTime_75th_percentile": 0,
> "SplitTime_90th_percentile": 0,
> "SplitTime_95th_percentile": 0,
> "SplitTime_98th_percentile": 0,
> "SplitTime_99th_percentile": 0,
> "SplitTime_99.9th_percentile": 0,
> Value of these will always be 0 since Split is happening Master side and 
> there is no Metrics update. 
>  
>  
> Update 1: After the fix, JMX is like this :
> { "name": "Hadoop:service=HBase,name=Master,sub=Procedure", "modelerType": 
> "Master,sub=Procedure", "tag.Context": "master", "tag.Hostname": 
> "blrphispra01257", "numMasterWALs": 0, "splitProcedure_RequestCount": 0, 
> "splitProcedure_FailedCount": 0, "splitProcedure_SuccessCount": 0, 
> "splitProcedureTime_num_ops": 0, "splitProcedureTime_min": 0, 
> "splitProcedureTime_max": 0, "splitProcedureTime_mean": 0, 
> "splitProcedureTime_25th_percentile": 0, "splitProcedureTime_median": 0, 
> "splitProcedureTime_75th_percentile": 0, 
> "splitProcedureTime_90th_percentile": 0, 
> "splitProcedureTime_95th_percentile": 0, 
> "splitProcedureTime_98th_percentile": 0, 
> "splitProcedureTime_99th_percentile": 0, 
> "splitProcedureTime_99.9th_percentile": 0 }
> ,
>  
> ,



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

Reply via email to