Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 28 Aug 2013 03:15:53 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12661115.1375359623366.44851.1377659753869@arcas>
In-Reply-To: <JIRA.12661115.1375359623366@arcas>
References: <JIRA.12661115.1375359623366@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5441) JobClient exit whenever RM issue
 Reboot command to 1st attempt App Master.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He updated MAPREDUCE-5441:
-------------------------------

    Status: Patch Available  (was: Open)
    
> JobClient exit whenever RM issue Reboot command to 1st attempt App Master.
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5441
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5441
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, client
>    Affects Versions: 2.0.5-alpha, 2.1.0-beta, 2.1.1-beta
>            Reporter: Rohith Sharma K S
>            Assignee: Jian He
>         Attachments: MAPREDUCE-5441.1.patch, MAPREDUCE-5441.patch
>
>
> When RM issue Reboot command to app master, app master shutdown gracefully. All the history event are writtent to hdfs with job status set as ERROR. Jobclient get job state as ERROR and exit. 
> But RM launches 2nd attempt app master where no client are there to get job status.In RM UI, job status is displayed as SUCCESS but for client Job is Failed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira