Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 3 Jul 2014 00:46:27 +0000 (UTC)
From: "Mayank Bansal (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12715815.1400695617613.92834.1404348387095@arcas>
In-Reply-To: <JIRA.12715815.1400695617613@arcas>
References: <JIRA.12715815.1400695617613@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5900) Container preemption interpreted
 as task failures and eventually job failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mayank Bansal updated MAPREDUCE-5900:
-------------------------------------

    Attachment: MAPREDUCE-5900-trunk-3.patch

Thanks [~zjshen] for the review.
Update Comments.

Thanks,
Mayank

> 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: Sub-task
>          Components: applicationmaster, mr-am, mrv2
>    Affects Versions: 2.4.1
>            Reporter: Mayank Bansal
>            Assignee: Mayank Bansal
>         Attachments: MAPREDUCE-5900-1.patch, MAPREDUCE-5900-branch-241-2.patch, MAPREDUCE-5900-trunk-1.patch, MAPREDUCE-5900-trunk-2.patch, MAPREDUCE-5900-trunk-3.patch
>
>
> We have Added preemption exit code needs to be incorporated
> MR needs to recognize the special exit code value of -102 and interpret it as a container being killed instead of a container failure.


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