[
https://issues.apache.org/jira/browse/HBASE-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917302#comment-16917302
]
Duo Zhang commented on HBASE-15867:
-----------------------------------
{quote}
For history, could be a column family that keeps data for a week or two? In
hbase:meta?
{quote}
By default I will always answer like this: the rowkey is in a different pattern
and it will mess up hbase:meta. But considering splittable meta, it seems that
I may find a way to deal with this.
We could add a special prefix in the row key for different system tables, and
make a special family for it. For example, for all the records in hbase:acl, we
could introduce a prefix like ':::acl:::', since we do not allow ':' in either
namespace or table name, so it will not conflict with the existing table
related records. And the family could be namd as 'acl'.
And we could make a special split policy that only splits at these special
prefixs, so it will not break any assumptions so far, as all the records for
the 'system table' are in the same region.
> 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
(v8.3.2#803003)
