hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16144) Replication queue's lock will live forever if RS acquiring the lock has died prematurely
Date Mon, 18 Jul 2016 07:01:20 GMT

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

Hudson commented on HBASE-16144:
--------------------------------

SUCCESS: Integrated in HBase-1.3 #786 (See [https://builds.apache.org/job/HBase-1.3/786/])
HBASE-16144 Replication queue's lock will live forever if RS acquiring (ud1937: rev 19ff9fa2d67464294b896f313ce89c4291e7ae81)
* hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestMultiSlaveReplication.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/cleaner/ReplicationZKLockCleanerChore.java


> 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: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 0.98.20, 1.1.6
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.21, 1.2.3, 1.1.7
>
>         Attachments: HBASE-16144-0.98.v1.patch, HBASE-16144-branch-1-v1.patch, HBASE-16144-branch-1-v2.patch,
HBASE-16144-branch-1.1-v1.patch, HBASE-16144-branch-1.1-v2.patch, HBASE-16144-v1.patch, HBASE-16144-v2.patch,
HBASE-16144-v3.patch, HBASE-16144-v4.patch, HBASE-16144-v5.patch, HBASE-16144-v6.patch, HBASE-16144-v6.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)

Mime
View raw message