[
https://issues.apache.org/jira/browse/HADOOP-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974500#comment-14974500
]
Chris Nauroth commented on HADOOP-12508:
----------------------------------------
Hello [~gouravk].
Thank you for posting this patch. However, I don't see how this could really
fix the problem. If a {{delete}} operation is failing because of another
concurrent process holding a lease, then I expect simply calling
{{acquireLease}} immediately would fail again, because it's impossible for 2
clients to hold a lease on the same blob at the same time. Perhaps it would
appear to work sometimes if sufficient time passed for the other process to
release its lease, but this would be a non-deterministic race condition.
Has the patch been tested?
> 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
>
>
> 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)
