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

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

Results for branch branch-1.3
        [build #576 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576//General_Nightly_Build_Report/]


(/) {color:green}+1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576//JDK7_Nightly_Build_Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576//JDK8_Nightly_Build_Report_(Hadoop2)/]




(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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)

Reply via email to