hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (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:27:29 GMT

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

Himanshu Vashishtha commented on HBASE-5222:
--------------------------------------------

@Josh: In case you want to do some maintenance on the slave cluster, while you do want to
resume the replication once it is restored, you don't need to pull the stop trigger. The master
cluster RS see that they can't connect to the slave cluster's RS anymore and will keep on
waiting till they are up (sleeping/awaking loop). 
But in case you are also stopping the slave cluster's ZK, then you might have to remove/add
it again. As the Master cluster just stops caring about it then.

There is also a jira in the upstream in which you can enable/disable a particular peer (HBase-3143).

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

PS: This is based on "few days using plus 1 day code digging (yesterday:)" experience. So,
let's see what JD says.
                
> 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

        

Mime
View raw message