[
https://issues.apache.org/jira/browse/MAPREDUCE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975008#comment-13975008
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-5848:
----------------------------------------------------
We should also expose a task-attempt-diagnostic which says the container got
preempted, that will help a bit.
bq. When a task attempt receives SIGTERM from the NM it causes the FileSystem
to close via the shutdown hook and often causes exceptions within the task.
I haven't seen this in YarnChild. Is FileSystem itself installing this?
> MapReduce counts forcibly preempted containers as FAILED
> --------------------------------------------------------
>
> Key: MAPREDUCE-5848
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5848
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Carlo Curino
> Assignee: Subramaniam Krishnan
> Attachments: YARN-1958.patch
>
>
> The MapReduce AM is considering a forcibly preempted container as FAILED,
> while I think it should be considered as KILLED (i.e., not count against the
> maximum number of failures).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
