[ https://issues.apache.org/jira/browse/HBASE-20695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513280#comment-16513280 ]
Guanghao Zhang edited comment on HBASE-20695 at 6/15/18 3:20 AM: ----------------------------------------------------------------- Pushed to master and branch-2. Thanks [~xucang] for contributing. And please use the jira id and jira title as the commit message in the future. Thanks. :-) was (Author: zghaobac): Pushed to master and branch-2. Thanks [~xucang] for contributing. And please use the jira id and jira title as the commit message. Thanks. :-) > Implement table level RegionServer replication metrics > ------------------------------------------------------- > > Key: HBASE-20695 > URL: https://issues.apache.org/jira/browse/HBASE-20695 > Project: HBase > Issue Type: Improvement > Components: metrics > Reporter: Xu Cang > Assignee: Xu Cang > Priority: Minor > Fix For: 2.1.0 > > Attachments: HBASE-20695.master.001.patch, > HBASE-20695.master.002.patch, HBASE-20695.master.003.patch, > HBASE-20695.master.004.patch, HBASE-20695.master.005.patch, > HBASE-20695.master.006.patch, HBASE-20695.master.007.patch, > HBASE-20695.master.008.patch, HBASE-20695.master.009.patch, > HBASE-20695.master.010.patch > > > Region server metrics now are mainly global metrics. It would be nice to have > table level metrics such as table level source.AgeOfLastShippedOp to indicate > operators which table's replication is lagging behind. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)