[
https://issues.apache.org/jira/browse/HDFS-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508035#comment-13508035
]
Daryn Sharp commented on HDFS-4248:
-----------------------------------
bq. As for what happens to the leases after renaming [...] I think namenode
should release them
I agree, I posed this question in the last paragraph of the first comment on
this jira. If Nicholas and others think that's the right to do, I can address
on another jira since I think this issue is a bit more severe.
bq. Does this jira supersede HDFS-2875?
Yes, I think it will. I filed this jira since it's a bit more than a simple
cleanup.
> Renames may cause dangling leases
> ---------------------------------
>
> Key: HDFS-4248
> URL: https://issues.apache.org/jira/browse/HDFS-4248
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: h4248_20121130_test_rename.patch,
> HDFS-4248.branch-0.23.patch, HDFS-4248.patch
>
>
> Renames of directories may incorrectly re-write the paths in leases under the
> tree being 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
