Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 14 Nov 2017 02:20:00 +0000 (UTC)
From: "Duo Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13116965.1510145501000.228052.1510626000186@Atlassian.JIRA>
In-Reply-To: <JIRA.13116965.1510145501000@Atlassian.JIRA>
References: <JIRA.13116965.1510145501000@Atlassian.JIRA> <JIRA.13116965.1510145501165@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-19216) Use procedure to execute
 replication peer related operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 14 Nov 2017 02:20:05 -0000


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

Duo Zhang commented on HBASE-19216:
-----------------------------------

Ping [~stack]. Need to know the state of procedure v2 and if there is already a plan to improve it? If no I will try to fix it by myself.

Thanks.

> Use procedure to execute replication peer related operations
> ------------------------------------------------------------
>
>                 Key: HBASE-19216
>                 URL: https://issues.apache.org/jira/browse/HBASE-19216
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Duo Zhang
>
> When building the basic framework for HBASE-19064, I found that the enable/disable peer is built upon the watcher of zk.
> The problem of using watcher is that, you do not know the exact time when all RSes in the cluster have done the change, it is a 'eventually done'. 
> And for synchronous replication, when changing the state of a replication peer, we need to know the exact time as we can only enable read/write after that time. So I think we'd better use procedure to do this. Change the flag on zk, and then execute a procedure on all RSes to reload the flag from zk.
> Another benefit is that, after the change, zk will be mainly used as a storage, so it will be easy to implement another replication peer storage to replace zk so that we can reduce the dependency on zk.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)