hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Created: (HDFS-862) Potential NN deadlock in processDistributedUpgradeCommand
Date Tue, 29 Dec 2009 16:56:29 GMT
Potential NN deadlock in processDistributedUpgradeCommand
---------------------------------------------------------

                 Key: HDFS-862
                 URL: https://issues.apache.org/jira/browse/HDFS-862
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: name-node
    Affects Versions: 0.22.0
            Reporter: Todd Lipcon


Haven't seen this in practice, but the lock order is inconsistent. processReport locks FSNamesystem,
then calls UpgradeManager.startUpgrade, getUpgradeState, and getUpgradeStatus (each of which
locks the UpgradeManager). FSNameSystem.processDistributedUpgradeCommand calls upgradeManager.processUpgradeCommand
which is synchronized on UpgradeManager, which can call FSNameSystem.leaveSafeMode which synchronizes
on FSNamesystem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message