hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19636) All rs should already start work with the new peer change when replication peer procedure is finished
Date Tue, 02 Jan 2018 08:30:00 GMT

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

Duo Zhang commented on HBASE-19636:
-----------------------------------

In ReplicationSourceManager, we will first add the newly created ReplicationSource to the
sources list, and then add the latestPaths to it, so I think here we can make sure that the
ReplicationSource will not miss any wal files.

And for removePeer it is also OK.

Need to confirm enablePeer, disablePeer and updatePeerConfig.

> 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
>
> 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)

Mime
View raw message