[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177304#comment-16177304
]
Zach York commented on HBASE-18775:
-----------------------------------
[~stack] Let me dive into where isReadOnly() is used. I *believe* that it is
being used by region replicas to turn off writes to that, but it was a while
ago that I actually investigated that so let me take another look.
Originally, I had decided to use 'global' since this did affect both the master
and RS so I wanted to use a single configuration. If you think it would make
more sense to drop the global keyword, I would be fine with that.
Also thanks for clarification on the stance towards ZK :) I had guessed most of
that, but didn't want to mislead anyone.
> 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,
> HBASE-18775.HBASE-18477.004.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)
