[ https://issues.apache.org/jira/browse/HBASE-17289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740679#comment-15740679 ]
Guanghao Zhang commented on HBASE-17289: ---------------------------------------- Thanks. This variable can be used in test, too. It is a different package org.apache.hadoop.hbase.client.replication. > Avoid adding a replication peer named "lock" > -------------------------------------------- > > Key: HBASE-17289 > URL: https://issues.apache.org/jira/browse/HBASE-17289 > Project: HBase > Issue Type: Bug > Components: Replication > Affects Versions: 1.3.0, 1.4.0, 1.1.7, 0.98.23, 1.2.4 > Reporter: Guanghao Zhang > Assignee: Guanghao Zhang > Priority: Minor > Attachments: HBASE-17289-branch-1.1.patch, > HBASE-17289-branch-1.2.patch, HBASE-17289-branch-1.3.patch, > HBASE-17289-branch-1.patch > > > When zk based replication queue is used and useMulti is false, the steps of > transfer replication queues are first add a lock, then copy nodes, finally > clean old queue and the lock. And the default lock znode's name is "lock". So > we should avoid adding a peer named "lock". -- This message was sent by Atlassian JIRA (v6.3.4#6332)