[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177341#comment-16177341
]
stack commented on HBASE-18775:
-------------------------------
Should writeup the ZK tendency (and all others -- smile).
You tell me, but I was hoping a single read-only flag would do for all cases.
If set on the region level, it'd not allow writes. If set on the process level
(in the hbase-*.xml), then the process would not take writes (if a
regionserver, it'd pass the read-only=true to all hosted regions, if a master,
it'd disallow writes).
Could be an issue if region-replicas want to turn off read-only for whatever
reason but hopefully the process-level flag would then prevail.
Just trying to have a single flag if possible (I think I got this notion from
you, a review you did of m master not-carrying-regions review -- smile).
> 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)
