[jira] [Updated] (HBASE-18374) RegionServer Metrics improvements

["stack (JIRA)" <ji...@apache.org>]

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

stack updated HBASE-18374:
--------------------------
    Fix Version/s:     (was: 3.0.0)

> RegionServer Metrics improvements
> ---------------------------------
>
>                 Key: HBASE-18374
>                 URL: https://issues.apache.org/jira/browse/HBASE-18374
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Abhishek Singh Chouhan
>            Assignee: Abhishek Singh Chouhan
>            Priority: Major
>             Fix For: 1.4.0, 2.0.0-alpha-2, 2.0.0
>
>         Attachments: HBASE-18374.branch-1.001.patch, HBASE-18374.branch-1.001.patch, HBASE-18374.branch-1.002.patch, HBASE-18374.branch-1.003.patch, HBASE-18374.master.001.patch, HBASE-18374.master.002.patch, HBASE-18374.master.003.patch, HBASE-18374.master.004.patch, HBASE-18374.master.005.patch
>
>
> At the RS level we have latency metrics for mutate/puts and deletes that are updated per batch (ie. at the end of entire batchop if it contains put/delete update the respective metric) in contrast with append/increment/get metrics that are updated per op. This is a bit ambiguous since the delete and put metrics are updated for multi row mutations that happen to contain a put/delete. We should rename the metric(eg. delete_batch)/add better description. Also we should add metrics for single delete client operations that come through RSRpcServer.mutate path. We should also add metrics for checkAndPut and checkAndDelete.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)