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 "Chris Douglas (JIRA)" <ji...@apache.org> on 2011/06/06 23:34:59 UTC
[jira] [Resolved] (MAPREDUCE-2535) JobClient creates a RunningJob
with null status and profile
[ https://issues.apache.org/jira/browse/MAPREDUCE-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas resolved MAPREDUCE-2535.
--------------------------------------
Resolution: Fixed
Committed the follow-up. Thanks for the quick fix.
> JobClient creates a RunningJob with null status and profile
> -----------------------------------------------------------
>
> Key: MAPREDUCE-2535
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2535
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.204.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: MR-2535-0.20.20X-V1.patch, MR-2535-failures-v1.patch
>
>
> Exception occurred because the job was retired and is removed from RetireJobCcahe and CompletedJobStatusStore. But, the
> JobClient creates a RunningJob with null status and profile, if getJob(JobID) is called again.
> So, Even-though not null check is there in the following user code, it did not help.
> 466 runningJob = jobClient.getJob(mapRedJobID);
> 467 if(runningJob != null) {
> JobClient.getJob() should return null if status is null.
> In trunk this is fixed by validating that the job status is not null every time it is updated, and also verifying that that the profile data is not null when created.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira