[jira] [Commented] (HBASE-7380) [replication] When transferring queues, check if the peer still exists before copying the znodes

["Chris Trezzo (JIRA)" <ji...@apache.org>]

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

Chris Trezzo commented on HBASE-7380:
-------------------------------------

[~jdcryans] I would agree. Since peerExists() is not exposed through an interface, and it doesn't depend on any functionality in ReplicationPeersZKImpl, it seems like ReplicationStateZKBase would be a good place for it.
                
> [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
>            Assignee: 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