[
https://issues.apache.org/jira/browse/HBASE-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527699#comment-16527699
]
Hudson commented on HBASE-19943:
--------------------------------
Results for branch master
[build #380 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/380/]: (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/master/380//General_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/master/380//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/380//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Only allow removing sync replication peer which is in DA state
> --------------------------------------------------------------
>
> Key: HBASE-19943
> URL: https://issues.apache.org/jira/browse/HBASE-19943
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-19943.HBASE-19064.001.patch,
> HBASE-19943.HBASE-19064.002.patch, HBASE-19943.HBASE-19064.002.patch
>
>
> To simplify the logic of RemovePeerProcedure. Otherwise we may also need to
> reopen regions which makes the RemovePeerProcedure can not fit for both sync
> and normal replication peer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
