hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5222) Stopping replication via the "stop_replication" command in hbase shell on a slave cluster isn't acknowledged in the replication sink
Date Fri, 23 Mar 2012 16:47:30 GMT

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

Jean-Daniel Cryans commented on HBASE-5222:

bq. So, let's see what JD says.

Here he goes:

bq. When you want to use replication, you ought to run these commands

Not sure which commands you're talking about. In the specific case of {{stop_replication}},
it's a kill switch in the proper sense (quote from wikipedia):

bq. a kill switch is designed and configured to a) completely abort the operation at all costs
and b) be operable in a manner that is quick, simple (so that even a panicking user with impaired
executive function can operate it), and, usually, c) be obvious even to an untrained operator
or a bystander

We hit on a) and b), the c) part might not be there yet. The issue here is that the command
is respected on the master cluster (when ran there) but not on the slave cluster (when ran

bq.  If you stop replication on the master, the logs are no longer stored to be pushed down
stream like they would with replication enabled.


bq. The bug, however, causes the slave to keep accepting logs even while disabled although
the other processes on slave cluster respect the disabled flag

Since it's a kill switch, what's going to happen is the slave cluster is going to *drop the
log edits*. This is not what you want, you want is HBASE-3134.

bq. So, afaik, running commands on the slave cluster are futile as its the master cluster
which does all the work.

I think you understand the issue here reasonably well, and indeed most of the commands won't
do anything on the slave cluster, except here the kill switch should stop all replication-related
activity including applying incoming logs.
> 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


View raw message