[
https://issues.apache.org/jira/browse/HBASE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236639#comment-13236639
]
Himanshu Vashishtha commented on HBASE-5222:
--------------------------------------------
@JD: When you want to use replication, you ought to run these commands (plus
setting replication hbase.replication to true in the hase-config.xml) on the
master cluster. The slave cluster configs is not changed (in case of simple
Master-slave replication).
So, in case when hbase.replication is false (or default) on the slave, its
replication specific code will be null, and make these commands non-effective;
no?
> Stopping replication via the "stop_replication" command in hbase shell on a
> slave cluster isn't acknowledged in the replication sink
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5222
> URL: https://issues.apache.org/jira/browse/HBASE-5222
> Project: HBase
> Issue Type: Bug
> Components: replication, shell
> Affects Versions: 0.90.4
> Reporter: Josh Wymer
>
> After running "stop_replication" in the hbase shell on our slave cluster we
> saw replication continue for weeks. Turns out that the replication sink is
> missing a check to get the replication state and therefore continued to write.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
