[
https://issues.apache.org/jira/browse/HDFS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082785#comment-13082785
]
Todd Lipcon commented on HDFS-2229:
-----------------------------------
It seems like FSNamesystem.activate should be writelocking itself before
calling setBlockTotal, maybe? Then it will already have the write lock and be
consistent with the usual order (FSN lock > SafeModeInfo lock). It also seems
to make intuitive sense - activating the FSN is definitely going to be making
state changes within it.
> Deadlock in NameNode
> --------------------
>
> Key: HDFS-2229
> URL: https://issues.apache.org/jira/browse/HDFS-2229
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Priority: Blocker
> Attachments: cycle1.png, cycle2.png, h2229_20110807.patch
>
>
> Either I am doing something incredibly stupid, or something about my
> environment is completely weird, or may be it really is a valid bug. I am
> running a NameNode deadlock consistently with 0.23 HDFS. I could never start
> NN successfully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
