You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ashwin Shankar (JIRA)" <ji...@apache.org> on 2014/06/19 02:05:24 UTC
[jira] [Commented] (MAPREDUCE-5848) MapReduce counts forcibly
preempted containers as FAILED
[ https://issues.apache.org/jira/browse/MAPREDUCE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036692#comment-14036692 ]
Ashwin Shankar commented on MAPREDUCE-5848:
-------------------------------------------
Committers,
can we please commit this if its looking good ?
I tried out this patch and it seems to work well.
Without this,jobs fail due to preemption after mapreduce.(map,reduce).maxattempts limit is reached.
This is also blocking YARN-1961.
> 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 Venkatraman 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)