[ 
https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701469#comment-16701469
 ] 

Duo Zhang commented on HBASE-21154:
-----------------------------------

The code for synchronous replication has only been merged to master branch so 
it can only be used in 3.0.

> 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
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21154-v1.patch, HBASE-21154-v2.patch, 
> HBASE-21154-v4.patch, HBASE-21154-v5.patch, HBASE-21154-v6.patch, 
> HBASE-21154-v7.patch, HBASE-21154.patch
>
>
> 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)

Reply via email to