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 "Thomas Marquardt (JIRA)" <ji...@apache.org> on 2018/01/03 23:13:00 UTC
[jira] [Commented] (HADOOP-15086) NativeAzureFileSystem file rename
is not atomic
[ https://issues.apache.org/jira/browse/HADOOP-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310454#comment-16310454 ]
Thomas Marquardt commented on HADOOP-15086:
-------------------------------------------
I will open a new JIRA and begin the backport to branch-2.
> 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
> Reporter: Shixiong Zhu
> Assignee: Thomas Marquardt
> Fix For: 3.1.0, 3.0.1
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org