[
https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850297#comment-16850297
]
Zheng Hu commented on HBASE-15867:
----------------------------------
bq. will we track peer changes in table or we only keep the current peer
information?
In our original desgin, we didn't plan to store the peer changes. I guess the
starting point that tracking the history changes because you want to debug the
peer related problems, maybe it's better for us to enable the debug log or
enhance the peer related log info. Of course, once we change to
hbase:replication table we can keep all versions in it then all history changes
can be accessed. Thanks.
> 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)
