[
https://issues.apache.org/jira/browse/HDFS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995374#comment-13995374
]
Colin Patrick McCabe commented on HDFS-4437:
--------------------------------------------
Marking this as a dupe of HDFS-6294, which addressed the issues we had with
moving files that were open for write. Feel free to reopen if there's
something more we should do here.
> 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 was sent by Atlassian JIRA
(v6.2#6252)
