You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Xu Cang (JIRA)" <ji...@apache.org> on 2019/08/13 00:21:00 UTC
[jira] [Commented] (HBASE-15867) Move HBase replication tracking
from ZooKeeper to HBase
[ https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905686#comment-16905686 ]
Xu Cang commented on HBASE-15867:
---------------------------------
Since this Jira is blocked by a [dead loop issue|https://issues.apache.org/jira/browse/HBASE-20166]. Should we take one step back and ask, what's *the real issue we want to solve* by moving it from ZK to HBase table?
( I guess we want to remove the dependency of ZK for this usecase and make saving those info in a more reliable media?)
Can we tackle those issues in different ways?
I tried to read thru Jira descriptions and comments to find my answer but failed. Can you shed some lights? thanks [~openinx]
> 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.14#76016)