hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3846) Namenode deadlock in branch-1
Date Thu, 23 Aug 2012 09:11:42 GMT
Tsz Wo (Nicholas), SZE created HDFS-3846:

             Summary: Namenode deadlock in branch-1
                 Key: HDFS-3846
                 URL: https://issues.apache.org/jira/browse/HDFS-3846
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: name-node
            Reporter: Tsz Wo (Nicholas), SZE
            Assignee: Brandon Li

Jitendra found out the following problem:
1. Handler : Acquires namesystem lock waits on SafemodeInfo lock at SafeModeInfo.isOn()
2. SafemodeMonitor : Calls SafeModeInfo.canLeave() which is synchronized so SafemodeInfo lock
is acquired, but this method also causes following call sequence needEnter() -> getNumLiveDataNodes()
-> getNumberOfDatanodes() -> getDatanodeListForReport() -> getDatanodeListForReport()
. The getDatanodeListForReport is synchronized with FSNamesystem lock.

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


View raw message