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-19216) Use procedure to execute replication peer related operations
Date Fri, 17 Nov 2017 02:55:00 GMT

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

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

Yes, we need something like a ReplicationPeers to keep all the peers at master side, and also
prevent concurrent modification on a give peer.

But I would like to make the reportProcedureDone more general. So procedure id will always
be presented, and also a serialized protobuf message. We can encode the peer id in the protobuf
message?

Anyway, it seems that we need to find the stored procedure event if we want to wake up a procedure.
Got it. Let me try to implement a create peer procedure.

Thanks sir, help a lot.

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

Mime
View raw message