Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4055418A3F for ; Sat, 31 Oct 2015 02:58:28 +0000 (UTC) Received: (qmail 11899 invoked by uid 500); 31 Oct 2015 02:58:28 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 11849 invoked by uid 500); 31 Oct 2015 02:58:27 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 11802 invoked by uid 99); 31 Oct 2015 02:58:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Oct 2015 02:58:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B34282C1F57 for ; Sat, 31 Oct 2015 02:58:27 +0000 (UTC) Date: Sat, 31 Oct 2015 02:58:27 +0000 (UTC) From: "Gaurav Kanade (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12508) delete fails with exception when lease is held on blob MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983770#comment-14983770 ] Gaurav Kanade commented on HADOOP-12508: ---------------------------------------- [~cnauroth] - I have rebased and fixed the tabs issue, but I don't see a Jenkins run yet so still waiting for validation. FOr the issue of test using hard-coded values to coordinate two threads, I believe I can work around this by having the original thread acquire the lease and then attempt a delete. IN the interval between these two steps it will kick off background thread which will merely wait for a fixed time and then release the lease. This should essentially simulate the situation; I have already verified this test fails without the patch and passes after > delete fails with exception when lease is held on blob > ------------------------------------------------------ > > Key: HADOOP-12508 > URL: https://issues.apache.org/jira/browse/HADOOP-12508 > Project: Hadoop Common > Issue Type: Bug > Reporter: Gaurav Kanade > Assignee: Gaurav Kanade > Priority: Blocker > Attachments: HADOOP-12484.05.patch, HADOOP-12508.01.patch, HADOOP-12508.02.patch, HADOOP-12508.03.patch, HADOOP-12508.04.patch > > > The delete function as implemented by AzureNativeFileSystem store attempts delete without a lease. In most cases this works but in the case of a dangling lease resulting out of say a process killed and leaving a lease dangling for a small period a delete attempted during this period simply crashes. This fix addresses the situation by re-attempting the delete after a lease acqusition in this case -- This message was sent by Atlassian JIRA (v6.3.4#6332)