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

Hudson commented on HBASE-19905:
--------------------------------

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.


> ReplicationSyncUp tool will not exit if a peer replication is disabled
> ----------------------------------------------------------------------
>
>                 Key: HBASE-19905
>                 URL: https://issues.apache.org/jira/browse/HBASE-19905
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.3.1
>            Reporter: Ashish Singhi
>            Assignee: Ashish Singhi
>            Priority: Major
>             Fix For: 1.5.0, 2.0.0-beta-2, 1.3.3, 1.4.2, 2.0.0
>
>         Attachments: HBASE-19905.patch
>
>
> In our test cluster we had two peer clusters, in which one peer cluster 
> replication was disabled. Now when used ReplicationSyncUp tool to replicate 
> the data to peer cluster, the tool replicated the data to the enabled peer 
> cluster but it was keep on retrying to replicate the data to disabled peer 
> cluster and hence it was not getting terminated. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to