[
https://issues.apache.org/jira/browse/HBASE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Wymer updated HBASE-5222:
------------------------------
Description: 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. (was: The problem showed itself when our /hbase/.oldlogs
directory was not being cleaned up on our slave cluster. Turns out we had
previously disabled replication manually by executing "stop_replication" in the
hbase shell. Therefore, the clean old logs task (among others) was honoring
that while the Replication Sink fails to check the same value. Therefore
replication was still being written to the slave cluster (via replication sink)
but the logs were being saved longer than the default 10 minutes as hbase
stores them when stop_replication has been executed until it has been started
again.)
Summary: Stopping replication via the "stop_replication" command in
hbase shell on a slave cluster isn't acknowledged in the replication sink
(was: Stopping replication via the "stop_replication" command in hbase shell on
a slave cluster doesn't prevent replication but does alter cleanup tasks)
> 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
> 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
