You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/14 00:37:01 UTC

[jira] [Commented] (HBASE-16947) Some improvements for DumpReplicationQueues tool

    [ https://issues.apache.org/jira/browse/HBASE-16947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720736#comment-16720736 ] 

Hudson commented on HBASE-16947:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #509 (See [https://builds.apache.org/job/HBase-1.3-IT/509/])
HBASE-16947 Some improvements for DumpReplicationQueues tool (apurtell: rev 3f9457c663df774cde882657d6bc4fd29795a79c)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/DumpReplicationQueues.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesClientZKImpl.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java


> 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: 1.4.0, 2.0.0
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Major
>             Fix For: 1.4.0, 0.98.24, 1.3.3, 2.0.0
>
>         Attachments: HBASE-16947-branch-1.patch, HBASE-16947-branch-1.patch, HBASE-16947-branch-1.patch, 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
(v7.6.3#76005)