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

Zach York commented on HBASE-18775:
-----------------------------------

[~tedyu] Can you clarify which File you are talking about for:

bq. +  private static final TableName TABLE_NAME = 
TableName.valueOf("TestGlobalReadOnly");

I changed TestGlobalReadOnly to try to create a non-default namespace. Perhaps 
if you have more comments on this, it would be better to do it in RB.

bq. +    config.setBoolean("hbase.testing.nonamespacemanager", true);
bq. Why is the above needed ?

This is actually unnecessary now. In branch-1 there was a NamespaceManager that 
would fail to initialize if the default and system namespaces weren't created 
and couldn't be created. This is not an issue anymore. I have updated the patch 
to reflect this.

> Add a Global Read-Only property to turn off all writes for the cluster
> ----------------------------------------------------------------------
>
>                 Key: HBASE-18775
>                 URL: https://issues.apache.org/jira/browse/HBASE-18775
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, regionserver
>    Affects Versions: HBASE-18477
>            Reporter: Zach York
>            Assignee: Zach York
>         Attachments: HBASE-18775.HBASE-18477.001.patch, 
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a 
> cluster. This patch extends the read only mode used by replication to disable 
> all data and metadata operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to