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/03/09 21:04:02 UTC
[jira] [Commented] (HBASE-19636) All rs should already start work
with the new peer change when replication peer procedure is finished
[ https://issues.apache.org/jira/browse/HBASE-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393573#comment-16393573 ]
Hudson commented on HBASE-19636:
--------------------------------
Results for branch branch-2
[build #465 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465/]: (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-2/465//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/branch-2/465//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/branch-2/465//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> All rs should already start work with the new peer change when replication peer procedure is finished
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-19636
> URL: https://issues.apache.org/jira/browse/HBASE-19636
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2, Replication
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-19636-HBASE-19397-v5.patch, HBASE-19636.HBASE-19397.001.patch, HBASE-19636.HBASE-19397.002.patch, HBASE-19636.HBASE-19397.003.patch, HBASE-19636.HBASE-19397.004.patch
>
>
> When replication peer operations use zk, the master will modify zk directly. Then the rs will asynchronous track the zk event to start work with the new peer change. When replication peer operations use procedure, need to make sure this process is synchronous. All rs should already start work with the new peer change when procedure is finished.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)