[
https://issues.apache.org/jira/browse/HBASE-16144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363786#comment-15363786
]
Phil Yang commented on HBASE-16144:
-----------------------------------
In this test class, three cluster share the same zk cluster. In the end of
testZKLockCleaner the cluster1 will be closed, so the shared zk is closed, too.
If we run testZKLockCleaner first and then testMultiSlaveReplication, the
closed zk will throw exception while creating utility2.startMiniCluster().
We can add a line "utility1.setZkCluster(miniZK);" in setUpBeforeClass to
prevent closing zk when we close the cluster.
I'll upload a new patch soon, for master and other branches. Thanks.
> Replication queue's lock will live forever if RS acquiring the lock has died
> prematurely
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-16144
> URL: https://issues.apache.org/jira/browse/HBASE-16144
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.1, 1.1.5, 0.98.20
> Reporter: Phil Yang
> Assignee: Phil Yang
> Attachments: HBASE-16144-v1.patch, HBASE-16144-v2.patch,
> HBASE-16144-v3.patch, HBASE-16144-v4.patch
>
>
> In default, we will use multi operation when we claimQueues from ZK. But if
> we set hbase.zookeeper.useMulti=false, we will add a lock first, then copy
> nodes, finally clean old queue and the lock.
> However, if the RS acquiring the lock crash before claimQueues done, the lock
> will always be there and other RS can never claim the queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
