[
https://issues.apache.org/jira/browse/HDFS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562866#comment-13562866
]
Brandon Li commented on HDFS-4437:
----------------------------------
I meant a "different client" in my previous comments. Basically, my point is,
if renaming revokes a lease, the client is overpowered.
For example, one random client renames one of the top directories. It basically
revokes all the leases granted to other clients under this directory. That is,
for any client wants to gain a lease of any file, it could just rename it and
then open it. Most likely it could get the lease immediately as long as it has
write permission.
> Clients should not retain leases on moved files
> -----------------------------------------------
>
> Key: HDFS-4437
> URL: https://issues.apache.org/jira/browse/HDFS-4437
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
>
> Moving open files and/or parent directories of open files will rewrite the
> leases to the new path. The client is not notified so future stream
> operations will fail. However, as long as the client keeps its lease active
> it will have a "lock" on the file in its new location. This is not good for
> a daemon.
> Leases should be released after the file is moved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
