hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2535) JobClient creates a RunningJob with null status and profile
Date Thu, 26 May 2011 16:03:47 GMT

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

Robert Joseph Evans updated MAPREDUCE-2535:

    Attachment: MR-2535-0.20.20X-V1.patch

Because this is not targeted for trunk, and Jenkins will try to run this against trunk here
are the test-patch results

     [exec] -1 overall.  
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 4 new or modified tests.
     [exec]     -1 javadoc.  The javadoc tool appears to have generated 1 warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec]     -1 Eclipse classpath. The patch causes the Eclipse classpath to differ from
the contents of the lib directories.

I don't know why it complains about the eclipse classpath or javadocs.  Both of those are
false positives.  The eclipse classpath did not change, and it is still 6 javadoc warnings.

> 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