[
https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604903#comment-16604903
]
Sean Busbey commented on HBASE-21154:
-------------------------------------
also could we document some considerations for the future about how we pick
"new CF in meta" versus "table in the hbase namespace"?
it sounds like "master needs it to start" -> "CF in meta"? anything else goes
in a table, given our scaling constraints on meta?
> Remove hbase:namespace table; fold it into hbase:meta
> -----------------------------------------------------
>
> Key: HBASE-21154
> URL: https://issues.apache.org/jira/browse/HBASE-21154
> Project: HBase
> Issue Type: Improvement
> Components: meta
> Reporter: stack
> Priority: Major
>
> Namespace table is a small system table. Usually it has two rows. It must be
> assigned before user tables but after hbase:meta goes out. Its presence
> complicates our startup and is a constant source of grief when for whatever
> reason, it is not up and available. In fact, master startup is predicated on
> hbase:namespace being assigned and will not make progress unless it is up.
> Lets just add a new 'ns' column family to hbase:meta for namespace.
> Here is a default ns table content:
> {code}
> hbase(main):023:0* scan 'hbase:namespace'
> ROW
> COLUMN+CELL
> default
> column=info:d, timestamp=1526694059106,
> value=\x0A\x07default
> hbase
> column=info:d, timestamp=1526694059461,
> value=\x0A\x05hbase
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
