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-19397) Design procedures for ReplicationManager to notify peer change event from master
Date Fri, 01 Dec 2017 08:09:00 GMT

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

Duo Zhang commented on HBASE-19397:
-----------------------------------

Please see HBASE-19216, where we have already discussed something about this.

Thanks.

> Design  procedures for ReplicationManager to notify peer change event from master
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-19397
>                 URL: https://issues.apache.org/jira/browse/HBASE-19397
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>
> After we store peer states / peer queues information into hbase table,   RS can not track
peer config change by adding watcher znode.   
> So we need design procedures for ReplicationManager to notify peer change event.   the
replication rpc interfaces which may be implemented by procedures are following: 
> {code}
> 1. addReplicationPeer
> 2. removeReplicationPeer
> 3. enableReplicationPeer
> 4. disableReplicationPeer
> 5. updateReplicationPeerConfig
> {code}
> BTW,  our RS states will still be store in zookeeper,  so when RS crash, the tracker
which will trigger to transfer queues of crashed RS will still be a Zookeeper Tracker.  we
need NOT implement that by  procedures.  
> As we will  release 2.0 in next weeks,  and the HBASE-15867 can not be resolved before
the release,  so I'd prefer to create a new feature branch for HBASE-15867. 



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

Mime
View raw message