hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11116) Allow ReplicationSink to write to tables when READONLY is set
Date Tue, 06 May 2014 03:36:26 GMT

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

Jean-Daniel Cryans commented on HBASE-11116:

I wonder if you could sort of enable that right now with ACLs. Basically, only the user that
runs hbase can write to the tables on the slave cluster, everyone else is disallowed.

> 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

View raw message