[
https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408115#comment-15408115
]
Joseph commented on HBASE-15867:
--------------------------------
Hello,
If you check out the latest master code, there should be a brief description of
the table in the Javadocs for ReplicationTableBase. But in general, we are
using an HBase table "hbase:replication" that uses a row key of the
concatenated peer-id and servername. We keep two special columns, an owner
column that describes which regionserver currently owns the peer and a history
column that describes who has adopted the queue in the past. Finally there are
just a bunch of columns mapping WAL files to their bit offsets. These columns
are all under a single column family. I would assume that the HRef's would just
be another column family with a structure similar to the WAL's? I think looking
back, it might make sense to move the "history" and "owner" columns into their
own family. Feel free to ping me if you have any other questions :)
> 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
> Reporter: Joseph
> Assignee: Joseph
>
> 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
(v6.3.4#6332)
