You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Dushyanth (JIRA)" <ji...@apache.org> on 2016/12/04 20:12:58 UTC

[jira] [Updated] (HADOOP-13675) Bug in return value for delete() calls in WASB

     [ https://issues.apache.org/jira/browse/HADOOP-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dushyanth updated HADOOP-13675:
-------------------------------
    Attachment: HADOOP-13675.003.patch

Thanks [~liuml07] for the review. I have addressed your comments for the previous patch and attached Patch 3.

Testing: The patch contains new test to verify the changes made. Also changes have been tested against live tests for the both Block Blobs and Page Blobs.

> Bug in return value for delete() calls in WASB
> ----------------------------------------------
>
>                 Key: HADOOP-13675
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13675
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: azure, fs/azure
>    Affects Versions: 2.8.0
>            Reporter: Dushyanth
>            Assignee: Dushyanth
>             Fix For: 2.9.0
>
>         Attachments: HADOOP-13675.001.patch, HADOOP-13675.002.patch, HADOOP-13675.003.patch
>
>
> Current implementation of WASB does not correctly handle multiple threads/clients calling delete on the same file. The expected behavior in such scenarios is only one of the thread should delete the file and return true, while all other threads should receive false. However in the current implementation even though only one thread deletes the file, multiple clients incorrectly get "true" as the return from delete() call..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org