[
https://issues.apache.org/jira/browse/HDFS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562869#comment-13562869
]
Daryn Sharp commented on HDFS-4437:
-----------------------------------
Isn't that a good thing though as opposed to nobody ever being able to get a
lease on the renamed files until the daemon is restarted?
> 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
