Zheng Hu created HBASE-19397:
--------------------------------
Summary: 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
Reporter: Zheng Hu
Assignee: Zheng Hu
After we store peer states / peer queues information into hbase table, RS can
not tracker 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)