[
https://issues.apache.org/jira/browse/HADOOP-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755163#action_12755163
]
Todd Lipcon commented on HADOOP-6240:
-------------------------------------
bq. The namenode does not keep track of files open for read, so between the
time that you get the file's block list from the namenode and then try to read
the first block another process could replace it and that first block might no
longer exist.
Good point - without reader leases the atomicity of rename is unimportant since
there's no consistency in the first place.
> Rename operation is not consistent between different implementations of
> FileSystem
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-6240
> URL: https://issues.apache.org/jira/browse/HADOOP-6240
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.21.0
>
>
> The rename operation has many scenarios that are not consistently implemented
> across file systems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
