[
https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850008#comment-16850008
]
Xu Cang commented on HBASE-15867:
---------------------------------
thanks [~openinx]! Good info!
One thing I want to discuss is, if we finish all tasks above mentioned, will we
track peer changes in table or we only keep the current peer information?
If no, should we also consider adding this? Peer changes are not that frequent,
storing all peer changes into a DB is very useful for understanding certain
system behavior. Lacking this information is a big disadvantage since we don't
log peer changes into logs either. So, when someone asks "what peers did this
cluster have during certain date", we just cannot answer it with proofs, which
is not good. Want to know what do you think about this and do you have solution
in some ways? [~openinx] thanks again.
> Move HBase replication tracking from ZooKeeper to HBase
> -------------------------------------------------------
>
> Key: HBASE-15867
> URL: https://issues.apache.org/jira/browse/HBASE-15867
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Affects Versions: 2.1.0
> Reporter: Joseph
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 2.3.0
>
>
> Move the WAL file and offset tracking out of ZooKeeper and into an HBase
> table called hbase:replication.
> The largest three new changes will be two classes ReplicationTableBase,
> TableBasedReplicationQueues, and TableBasedReplicationQueuesClient. As of now
> ReplicationPeers and HFileRef's tracking will not be implemented. Subtasks
> have been filed for these two jobs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
