[
https://issues.apache.org/jira/browse/MAPREDUCE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974973#comment-13974973
]
Carlo Curino commented on MAPREDUCE-5848:
-----------------------------------------
Jason, thanks for moving to MR.. I mislabel it.
Regarding your comment, I was suspecting that something like that was going one
(hence my doubting the patch was enough).
On the positive side, the AM should know the containers was on the short-list
to be killed from previous preemption messages it received
so maybe it could count a failure of a container "doomed" by preemption as a
kill? Or simply postpone the decision on FAIL/KILL. Not sure...
I don't have time to look at this now, but if you provide a fix I am happy to
help you validate it (for different reasons we are testing preemption
under rather extreme scenarios).
> 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)
