[
https://issues.apache.org/jira/browse/HADOOP-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Marquardt updated HADOOP-15086:
--------------------------------------
Attachment: HADOOP-15086-002.patch
Attaching HADOOP-15086-002.patch. Steve, this updates the previous patch with
the changes that you recommended to the new test. Thanks!
The behavior of rename is not covered very well by the contract tests, is it?
I also cannot find a good description of the contract for rename, but maybe I'm
looking in the wrong place. Would be good to have to ensure rename is doing
the right things.
All tests are passing with the new patch against my US West 2 storage account.
I also verified that unexpected exceptions in the new test case will cause the
test to fail with nice diagnostic messages.
Tests run: 765, Failures: 0, Errors: 0, Skipped: 81
> NativeAzureFileSystem file rename is not atomic
> -----------------------------------------------
>
> Key: HADOOP-15086
> URL: https://issues.apache.org/jira/browse/HADOOP-15086
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 2.7.3
> Reporter: Shixiong Zhu
> Assignee: Thomas Marquardt
> Attachments: HADOOP-15086-001.patch, HADOOP-15086-002.patch,
> RenameReproducer.java
>
>
> When multiple threads rename files to the same target path, more than 1
> threads can succeed. It's because check and copy file in `rename` is not
> atomic.
> I would expect it's atomic just like HDFS.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
