[
https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848020#comment-16848020
]
Zheng Hu commented on HBASE-15867:
----------------------------------
[~xucang], Thanks for your attention. For this feature, the core obstacle is
the problem described in HBASE-20166. We've also have a discussion in mail
list with title: *[DISCUSS] A Problem When Start HBase Cluster Using Table
Based Replication* , You can see that.
Thought about the solution before, we may need to refactor the master/RS
startup procedure, seems lots of change. After some evaluation we thought that
the HBase 2.x stability and performance was worth spending more time at that
time, so we made the priority
of this feature not so high. Maybe it's the time for now :-) If you have
some time now, yeah, can resume this effort.
For myself, I'm mainly absorbed in HBASE-21879. Once all those subtasks get
resolved , maybe I give a hand for this feature.
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)
