[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177626#comment-16177626
]
Ashish Singhi commented on HBASE-18775:
---------------------------------------
bq. I'd like to hear your pros/cons for each approach, perhaps there is
something I'm missing.
conf.get is a little expensive operation I think and if some user is not using
this feature then unnecessarily it will add some time to operations. Another
point is from maintenance point of view if tomorrow some new operation is being
added then we may miss to add this check in that operation. If its a CP thing
then from class level document it will be clear what needs to be done in the
operation hook call to handle this feature.
Is it possible to make this configuration a dynamic one ?
Instead of throwing DoNotRetryIOException can we throw AccessDeniedException,
what do you say ?
> 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)
