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 "Mayank Bansal (JIRA)" <ji...@apache.org> on 2014/05/21 20:07:40 UTC

[jira] [Created] (MAPREDUCE-5900) Container preemption interpreted as task failures and eventually job failures

Mayank Bansal created MAPREDUCE-5900:
----------------------------------------

             Summary: Container preemption interpreted as task failures and eventually job failures 
                 Key: MAPREDUCE-5900
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5900
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: applicationmaster, mr-am, mrv2
    Affects Versions: 2.0.2-alpha
            Reporter: Mayank Bansal
            Assignee: Sandy Ryza
             Fix For: 2.1.0-beta


When YARN reports a completed container to the MR AM, it always interprets it as a failure.  This can lead to a job failing because too many of its tasks failed, when in fact they only failed because the scheduler preempted them.

MR needs to recognize the special exit code value of -100 and interpret it as a container being killed instead of a container failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)