[
https://issues.apache.org/jira/browse/MAPREDUCE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837623#action_12837623
]
Amareshwari Sriramadasu commented on MAPREDUCE-1499:
----------------------------------------------------
All the methods in jcarder graphs : assignTasks(), finalizeJob(),
getSetupCleanupTasks() are in a heartbeat which is under JobTracker lock.
Since, everything is under JobTracker lock, there is no deadlock. Am I missing
any thing, here?
MAPREDUCE-805 fixes a deadlock to do with initJob() and finalizeJob() in branch
0.20.1.
> 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.
