[
https://issues.apache.org/jira/browse/MAPREDUCE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838040#action_12838040
]
Aaron Kimball commented on MAPREDUCE-1499:
------------------------------------------
Amar,
Thanks for the clarification. I believed there were other instances where there
was a lock ordering of TS-> JIP without the JT gate, but it seems now that this
is only in the fair scheduler. I went back and ran tests again and the deadlock
cycle did not reproduce in the FIFO scheduler with or without the patch. (We
can't get jcarder to regenerate the attached graphs with the FIFO scheduler, so
it seems as though this issue is a false alarm.)
I'm going to close this as Cant-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.
