[
https://issues.apache.org/jira/browse/HADOOP-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975419#comment-14975419
]
Chris Nauroth commented on HADOOP-12508:
----------------------------------------
[~gouravk], thank you for adding the test, but this doesn't really cover
execution of the new logic. (The test passes with and without the main code
change applied.) I think the idea behind the test could be made to work if the
lease was acquired in a background thread, and then the main JUnit thread
attempted the delete. We'd then expect the new logic to wait on its own lease
acquisition and eventually complete the delete.
> 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-12508.01.patch, HADOOP-12508.02.patch,
> HADOOP-12508.03.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)
