hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (MAPREDUCE-2535) JobClient creates a RunningJob with null status and profile
Date Mon, 06 Jun 2011 21:07:00 GMT

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

Robert Joseph Evans reopened MAPREDUCE-2535:

The fix is good, but it broke the system tests.  Reopening the bug to add in a patch to fix
the tests.

> 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:
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>         Attachments: MR-2535-0.20.20X-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
> 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

View raw message