[
https://issues.apache.org/jira/browse/HBASE-16947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613812#comment-15613812
]
Guanghao Zhang commented on HBASE-16947:
----------------------------------------
Thanks for committing. HBASE-16450 was only merged to master and branch-1.3.
And now branch-1.3 is ready for release, so I didn't attach a patch for 1.3.
This improvement need HBASE-16450 was merged to all branches first. I'd like to
help to backport HBASE-16450 and this to all active branches. Does it need to
open a new issue? Thanks.
> Some improvements for DumpReplicationQueues tool
> ------------------------------------------------
>
> Key: HBASE-16947
> URL: https://issues.apache.org/jira/browse/HBASE-16947
> Project: HBase
> Issue Type: Improvement
> Components: Operability, Replication
> Affects Versions: 2.0.0, 1.4.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Attachments: HBASE-16947-v1.patch, HBASE-16947.patch
>
>
> Recently we met too many replication WALs problem in our production cluster.
> We need the DumpReplicationQueues tool to analyze the replication queues info
> in zookeeper. So I backport HBASE-16450 to our branch based 0.98 and did some
> improvements for it.
> 1. Show the dead regionservers under replication/rs znode. When there are too
> many WALs under znode, it can't be atomic transferred to new rs znode. So the
> dead rs znode will be leaved on zookeeper.
> 2. Make a summary about all the queues that belong to peer has been deleted.
> 3. Aggregate all regionservers' size of replication queue. Now the
> regionserver report ReplicationLoad to master, but there were not a aggregate
> metrics for replication.
> 4. Show how many WALs which can not found on hdfs. But the reason (WAL Not
> Found) need more time to dig.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
