[
https://issues.apache.org/jira/browse/HBASE-11116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-11116.
------------------------------------
Resolution: Won't Fix
Sounds reasonable. Resolving
> Allow ReplicationSink to write to tables when READONLY is set
> -------------------------------------------------------------
>
> Key: HBASE-11116
> URL: https://issues.apache.org/jira/browse/HBASE-11116
> Project: HBase
> Issue Type: New Feature
> Components: regionserver, Replication
> Reporter: Geoffrey Anderson
>
> A common practice with MySQL replication is to enable the read_only flag
> (http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_read_only)
> on slaves in order to disallow any user changes to a slave, while allowing
> replication from the master to flow in. In HBase, enabling the READONLY
> field on a table will cause ReplicationSink to fail to apply changes. It'd
> be ideal to have the default behavior allow replication to continue going
> through, a configurable option to influence this type of behavior, or perhaps
> even a flag that manipulates a peer's state (e.g. via add_peer) that dictates
> if replication can write to READONLY tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
