[
https://issues.apache.org/jira/browse/HDFS-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508048#comment-13508048
]
Tsz Wo (Nicholas), SZE commented on HDFS-4247:
----------------------------------------------
> ... but will this cause any future callers of getINodesUnderConstruction to
> encounter iteration errors if sortedLeasesByPath is modified by someone not
> synchronizing on the lease manager object but instead relying on the
> synchronization of the lease manager's methods?
I don't quite understand this. Are synchronization on the lease manager object
and lease manager's methods the same thing?
> saveNamespace should be tolerant of dangling lease
> --------------------------------------------------
>
> Key: HDFS-4247
> URL: https://issues.apache.org/jira/browse/HDFS-4247
> 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
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
> Attachments: HDFS-4247.branch-0.23.patch, HDFS-4247.patch
>
>
> Dangling leases to non-existent paths cause the NN to fail to start.
--
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
