hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1499) JobTracker.finalizeJob inverts lock order and causes potential deadlock
Date Wed, 17 Feb 2010 08:36:29 GMT

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

Todd Lipcon updated MAPREDUCE-1499:
-----------------------------------

    Attachment: jcarder_result_8.dot.png
                jcarder_result_1.dot.png

Just attaching two of the jcarder graphs. There are 12 cycles, but they're all essentially
the same issue.

This was fixed by MAPREDUCE-870 in branch-21 and trunk.

> 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
>         Attachments: jcarder_result_1.dot.png, jcarder_result_8.dot.png
>
>
> 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.


Mime
View raw message