[
https://issues.apache.org/jira/browse/HDFS-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094487#comment-14094487
]
Colin Patrick McCabe commented on HDFS-6757:
--------------------------------------------
bq. So far I plan to change the code so that the NN bails out when it fails to
replay the OP_CLOSE operations?
Sounds good.
bq. Colin Patrick McCabe, do you have anything specific that you want to
address?
I think we should continue to store the path in the op, as Daryn suggested.
This will make inotify more useful, since we'll have path information, while
still allowing us to get the benefits of increased efficiency by
lookup-by-inode ID.
> Simplify lease manager with INodeID
> -----------------------------------
>
> Key: HDFS-6757
> URL: https://issues.apache.org/jira/browse/HDFS-6757
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-6757.000.patch, HDFS-6757.001.patch,
> HDFS-6757.002.patch, HDFS-6757.003.patch, HDFS-6757.004.patch
>
>
> Currently the lease manager records leases based on path instead of inode
> ids. Therefore, the lease manager needs to carefully keep track of the path
> of active leases during renames and deletes. This can be a non-trivial task.
> This jira proposes to simplify the logic by tracking leases using inodeids
> instead of paths.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
