Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Wed, 31 Aug 2011 07:05:10 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <576727027.1712.1314774310103.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1951084457.7869.1314717341431.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (MAPREDUCE-2914) Killed and Failed jobs are not
 handled correctly with NotRunningJobs and should be served by the History
 Server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli reopened MAPREDUCE-2914:
------------------------------------------------


I also doubted this originally, but I missed the fact that for apps(not jobs) which are killed/failed, JobHistory is most likely garbled.

We still need to make sure that JobStatus fields like user, jobName, jobFile, trackingUrl etc are correct for these jobs whose corresponding apps got killed/failed.

Will update the title accordingly.

> Killed and Failed jobs are not handled correctly with NotRunningJobs and should be served by the History Server
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2914
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2914
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Jeffrey Naisbitt
>
> Jobs that are that are killed or failed should be served by historyServer rather than returning the "singleton" NotRunningJob instance for that state.  Otherwise, if someone does a getJob() on a killed/failed job, he won't get the correct information at all.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira