[
https://issues.apache.org/jira/browse/HDFS-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076796#comment-14076796
]
Brandon Li commented on HDFS-6757:
----------------------------------
When INode ID was introduced a year ago, one concern was the debug could be a
bit more difficult. For example, the following trace may not help debug that
much when error happens.
{noformat}
- LOG.debug(src + " not found in lease.paths (=" + lease.paths + ")");
+ LOG.debug("inode " + inodeId + " not found in lease.files (=" + lease
+ + ")");
{noformat}
It can be helpful to have the full path logged once or two in some places.
> Simplify lease manager with INodeID
> -----------------------------------
>
> Key: HDFS-6757
> URL: https://issues.apache.org/jira/browse/HDFS-6757
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-6757.000.patch, HDFS-6757.001.patch,
> HDFS-6757.002.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)
