[
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)
