Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A2A09200B51 for ; Mon, 18 Jul 2016 04:03:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A1293160A7C; Mon, 18 Jul 2016 02:03:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E9B8A160A6B for ; Mon, 18 Jul 2016 04:03:22 +0200 (CEST) Received: (qmail 32687 invoked by uid 500); 18 Jul 2016 02:03:21 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 32258 invoked by uid 99); 18 Jul 2016 02:03:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2016 02:03:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id F3AA82C037E for ; Mon, 18 Jul 2016 02:03:20 +0000 (UTC) Date: Mon, 18 Jul 2016 02:03:20 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16144) Replication queue's lock will live forever if RS acquiring the lock has died prematurely MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 18 Jul 2016 02:03:23 -0000 [ https://issues.apache.org/jira/browse/HBASE-16144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-16144: ------------------------------ Affects Version/s: (was: 1.1.5) (was: 1.2.1) 1.1.6 1.4.0 1.3.0 2.0.0 1.2.2 > 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)