[
https://issues.apache.org/jira/browse/MAPREDUCE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837851#action_12837851
]
Todd Lipcon commented on MAPREDUCE-1499:
----------------------------------------
I agree with Amar that if the inversion is gated by the JT lock then there is
no deadlock potential. JCarder, in theory, is supposed to detect the gating
lock and ignore the cycle. Let me look into the jcarder side of this a bit more
and see if it's a bug there or if we are missing something.
> 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.
