[ https://issues.apache.org/jira/browse/HBASE-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669267#comment-16669267 ]
Wellington Chevreuil commented on HBASE-21131: ---------------------------------------------- I believe this is a duplicate of HBASE-16870, where the issue is apparently fixed by the extra account for metrics of recovery queues sources. > HBase shell 'status replication' command does not track recovery replication > in sizeOfLogQueue > ---------------------------------------------------------------------------------------------- > > Key: HBASE-21131 > URL: https://issues.apache.org/jira/browse/HBASE-21131 > Project: HBase > Issue Type: Bug > Affects Versions: 1.2.0 > Reporter: Mitch Barnett > Assignee: Guangxu Cheng > Priority: Minor > > If replication is enabled for HBase and a RegionServer is restarted, it's > replication queue will be moved to another RegionServer. > When checking the 'dumpReplicationQueue' output, it's clearly visible the > total size of the recovery replication which is left on the RegionServer that > took over. > However, the 'status replication' command in hbase shell does not list any > difference in the 'sizeOfLogQueue' - in most cases it remains at or near 0. > Filing this JIRA as a bug since (in theory) 'status replication' should > include that recovered replication queue in the sizeOfLogQueue output. -- This message was sent by Atlassian JIRA (v7.6.3#76005)