[
https://issues.apache.org/jira/browse/HBASE-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310685#comment-16310685
]
Guanghao Zhang commented on HBASE-19636:
----------------------------------------
Make the Synchronization specification clear in ReplicationSourceManager. Now
only have two things need synchronization. For normal replication source, need
synchronized on latestPaths to avoid the new open source miss new log. For
recovered sources, need synchronized on oldSources to avoid adding recovered
source for the to-be-removed peer.
> 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
> Attachments: HBASE-19636.HBASE-19397.001.patch,
> HBASE-19636.HBASE-19397.002.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)
