[
https://issues.apache.org/jira/browse/HBASE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236692#comment-13236692
]
Josh Wymer commented on HBASE-5222:
-----------------------------------
@HV, @JD: Please correct me if I'm wrong here. If you stop replication on the
master, the logs are no longer stored to be pushed down stream like they would
with replication enabled. Instead they would be cleaned up based on the default
timeout. If we need to stop replicating to a slave cluster for maintenance, etc
we don't want the master throwing away non-replicated logs (thinking it has no
need to keep them). The bug, however, causes the slave to keep accepting logs
even while disabled although the other processes on slave cluster respect the
disabled flag.
> 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
