[
https://issues.apache.org/jira/browse/HBASE-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans updated HBASE-7380:
--------------------------------------
Attachment: HBASE-7380-0.94.patch
Here's a 0.94 patch.
For 0.96 I'm not sure how to go about this. [~ctrezzo], it seems that I would
need to put this in ReplicationQueuesZKImpl but it has no clue regarding peers.
Would it make sense to put peerExists() in ReplicationStateZKBase?
> [replication] When transferring queues, check if the peer still exists before
> copying the znodes
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-7380
> URL: https://issues.apache.org/jira/browse/HBASE-7380
> Project: HBase
> Issue Type: Bug
> Components: Replication, Usability
> Affects Versions: 0.94.3
> Reporter: Jean-Daniel Cryans
> Fix For: 0.95.1
>
> Attachments: HBASE-7380-0.94.patch
>
>
> Right now it's a pain if you remove a peer and still have rogue queues
> because they get moved on and on and on. NodeFailoverWorker needs to run the
> check:
> bq. if (!zkHelper.getPeerClusters().containsKey(src.getPeerClusterId())) {
> before this:
> bq. SortedMap<String, SortedSet<String>> newQueues =
> zkHelper.copyQueuesFromRS(rsZnode);
> And test.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
