[
https://issues.apache.org/jira/browse/HBASE-22938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917465#comment-16917465
]
Zach York commented on HBASE-22938:
-----------------------------------
Does this overly complicate the meta table?
Would this make recovery more difficult? (specifically the case where the meta
table is out of wack)
I imagine that system tables will continue to pop up because they are powerful.
I do think we would certainly need splittable meta for this to be considered as
it could quickly become a bottleneck.
An interesting proposal to help with the assignment woes, but I need to spend
some time thinking of potential implications of this.
> 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.2#803003)
