[
https://issues.apache.org/jira/browse/HADOOP-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983612#comment-14983612
]
Chris Nauroth commented on HADOOP-12508:
----------------------------------------
Assuming the patch gets rebased, but stays basically the same:
# I can tell it's going to fail the pre-commit checks because of indentation.
Please consistently indent by 2 spaces, not tabs.
# Using hard-coded sleep times to coordinate 2 threads is non-deterministic.
This will be prone to intermittent spurious test failures. A good
alternative is
[CountDownLatch|http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/CountDownLatch.html],
which allows you to block one thread waiting for another thread to complete
its work and then signal.
> 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, 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)
