[
https://issues.apache.org/jira/browse/MAPREDUCE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011858#comment-14011858
]
Carlo Curino commented on MAPREDUCE-5848:
-----------------------------------------
Mayank, I think you are right the behavior is equivalent at the moment. The
advantage of tracking TA_PREEMPTED explicitly is that in the future we will be
able to have different behaviors for preempted or killed tasks,
without having to parse the diagnostic message. This seems to ease future work
on this, so I would lean towards keeping the patch with this enrichement of the
state machine unless something else is problematic with it.
> 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: Sub-task
> Affects Versions: 2.1.0-beta
> Reporter: Carlo Curino
> Assignee: Subramaniam Krishnan
> Attachments: MR-5848.patch, MR-5848.patch, 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)
