You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Uma Maheswara Rao G (Commented) (JIRA)" <ji...@apache.org> on 2011/11/29 12:01:40 UTC
[jira] [Commented] (HDFS-1241) Possible deadlock between
LeaseManager and FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159192#comment-13159192 ]
Uma Maheswara Rao G commented on HDFS-1241:
-------------------------------------------
Just having a quick look at this,
LeaseManager.findPath() will be invoked by committBlockSynchronization,completeFile, updatePipeline, they are already aquired lock on fsNameSystem.
FSDirectory.unprotectedDelete will be invoked from FSNameSystem#delete api, whihc is already aquired the lock on fsnamesystem.
One more palce is loadEditsRecords, which should be at start.
I think dead lock may not be possible here.
Do you see any other problem here? am i missing some thing here?
Thanks
Uma
> Possible deadlock between LeaseManager and FSDirectory
> ------------------------------------------------------
>
> Key: HDFS-1241
> URL: https://issues.apache.org/jira/browse/HDFS-1241
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.20.2, 0.21.0
> Reporter: Todd Lipcon
> Attachments: leasemanager.png
>
>
> LeaseManager.findPath() locks LeaseManager, then FSDirectory by caling getFileINode. FSDirectory.unprotectedDelete locks itself and then calls LeaseManager.removeLeaseWithPrefixPath. This cycle could deadlock.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira