[jira] [Comment Edited] (HBASE-19636) All rs should already start work with the new peer change when replication peer procedure is finished

["Duo Zhang (JIRA)" <ji...@apache.org>]

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

Duo Zhang edited comment on HBASE-19636 at 1/5/18 6:07 AM:
-----------------------------------------------------------

Pushed to branch HBASE-19397. Thanks [~zghaobac] for contributing.


was (Author: apache9):
Pushed to branch HBASE-19397. Thanks [~zghaobac] for reviewing.

> 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
>             Fix For: HBASE-19397
>
>         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
(v6.4.14#64029)