You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2009/12/29 17:56:29 UTC

[jira] Created: (HDFS-862) Potential NN deadlock in processDistributedUpgradeCommand

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.