[
https://issues.apache.org/jira/browse/TEZ-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221046#comment-15221046
]
Bikas Saha commented on TEZ-3193:
---------------------------------
This is probably a leftover of removal of such reverse calls. There were more
of them and some were removed by making sure that such objects/members are
available locally to the TaskAttemptImpl (from the Task passed in via the
constructor) instead of calling back into the task to get this object/members.
Hence, task location hint and taskSpec could be passed in via the constructor
and referenced locally.
Doing this helps other future scenarios as well. If the TA location hint is
passed in via a constructor then it could be made different for each attempt.
E.g. remove the machine for v.1 from the location hint of v.2 for a speculative
execution so that speculated attempt does not end up on the same machine. There
is a jira for open for this.
Similarly, change the spec of v.1 have higher memory than the default for that
vertex because v.0 died with OOM.
> Deadlock in AM during task commit request
> -----------------------------------------
>
> Key: TEZ-3193
> URL: https://issues.apache.org/jira/browse/TEZ-3193
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.1, 0.8.2
> Reporter: Jason Lowe
> Priority: Blocker
>
> The AM can deadlock between TaskImpl and TaskAttemptImpl. Stacktrace and
> details in a followup comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
