You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/02/17 09:34:27 UTC

[jira] Created: (MAPREDUCE-1499) JobTracker.finalizeJob inverts lock order and causes potential deadlock

JobTracker.finalizeJob inverts lock order and causes potential deadlock
-----------------------------------------------------------------------

                 Key: MAPREDUCE-1499
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1499
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: jobtracker
    Affects Versions: 0.20.1, 0.20.2
            Reporter: Todd Lipcon
            Priority: Critical


This issue was brought up by Matei in MAPREDUCE-1436 as a fairsched bug, but it turns out it's a JT bug even with the fifo scheduler in unpatched 0.20.2. JobTracker.finalizeJob locks JT.jobs, JT.taskScheduler, etc, having gotten the JIP log before the JT lock.

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

[jira] Resolved: (MAPREDUCE-1499) JobTracker.finalizeJob inverts lock order and causes potential deadlock

Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron Kimball resolved MAPREDUCE-1499.
--------------------------------------

    Resolution: Cannot Reproduce

> JobTracker.finalizeJob inverts lock order and causes potential deadlock
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1499
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1499
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.1, 0.20.2
>            Reporter: Todd Lipcon
>            Assignee: Aaron Kimball
>            Priority: Critical
>         Attachments: jcarder_result_1.dot.png, jcarder_result_8.dot.png, MAPREDUCE-1499.patch
>
>
> This issue was brought up by Matei in MAPREDUCE-1436 as a fairsched bug, but it turns out it's a JT bug even with the fifo scheduler in unpatched 0.20.2. JobTracker.finalizeJob locks JT.jobs, JT.taskScheduler, etc, having gotten the JIP log before the JT lock.

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