[
https://issues.apache.org/jira/browse/HADOOP-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974999#comment-14974999
]
Gaurav Kanade commented on HADOOP-12508:
----------------------------------------
[~cnauroth]
Yes this could be potentially an improvement to break the lease explicitly. As
of now I have tried to follow the principle of minimum disruption to existing
code. As can be seen we never hit this scenario until this new HDP 2.3 test was
written though the scenario was valid since the beginning. So it might be
pretty rare case.
I believe in the light of the recent weeks experience we plan to take a re-look
at the WASB driver code from point of view of robustness to concurrency process
and test coverage; at that time we can revisit this issue.
Meanwhile on the test front I am planning to write a test that at least
partially validates this patch - i.e. tests that we are catching the exception
appropriately and submitting a new patch shortly. We still will not be able to
test the handling part as this will require extra infra.
Adding [~onpduo], [~pravinmittal], [~linchan] for their thoughts on your
suggestion.
> 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)
