hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3846) Namenode deadlock in branch-1
Date Thu, 23 Aug 2012 22:25:42 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jitendra Nath Pandey updated HDFS-3846:
---------------------------------------

    Affects Version/s:     (was: 1.1.0)
                       1.2.0
        Fix Version/s: 1.2.0

Committed to branch-1. Thanks to Brandon.
                
> 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
>    Affects Versions: 1.2.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Brandon Li
>             Fix For: 1.2.0
>
>         Attachments: HDFS-3846.branch-1.patch
>
>
> 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

        

Mime
View raw message