[
https://issues.apache.org/jira/browse/HBASE-22938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212603#comment-17212603
]
Michael Stack edited comment on HBASE-22938 at 10/12/20, 7:15 PM:
------------------------------------------------------------------
Just to repeat note added on HBASE-15867, some of the obstacles noted above
have been undone; i.e. region replicas are working to make it so they do not
need to keep state (see '4.1 Skip maintaining zookeeper replication queue
(offsets/WALs)' in
https://docs.google.com/document/d/1jJWVc-idHhhgL4KDRpjMsQJKCl_NRaCLGiH3Wqwd3O8/edit#heading=h.5hn1d8pikvrr).
Folding all system tables into hbase:meta should run a bit smoother (with
asserts as suggested above that we do not replicate system/catalog tables).
was (Author: stack):
{quote}This will make the read replicas feature can not 100% work for meta and
system tables, as we can not use in-cluster replication for them to spread the
edits to the secondary replicas any more.
{quote}
IIUC, this was once the case but no longer given read replicas no longer keep
ongoing state (see '4.1 Skip maintaining zookeeper replication queue
(offsets/WALs)' in
https://docs.google.com/document/d/1jJWVc-idHhhgL4KDRpjMsQJKCl_NRaCLGiH3Wqwd3O8/edit#heading=h.5hn1d8pikvrr)
> Fold all the system tables to hbase:meta
> ----------------------------------------
>
> Key: HBASE-22938
> URL: https://issues.apache.org/jira/browse/HBASE-22938
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Duo Zhang
> Priority: Major
>
> Quote my post on HBASE-15867 here, on how to deal with the dead lock when we
> want to store replication queues to hbase:replication table.
> {quote}
> 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.
> {quote}
> And I think there are also other advantages, for example the start up logic
> can be greatly simplified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
