Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 1 Dec 2011 21:50:40 +0000 (UTC)
From: "Alejandro Abdelnur (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1901226959.32822.1322776240955.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1238015603.20563.1322529100100.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3479) JobClient#getJob cannot find
 local jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161218#comment-13161218 ] 

Alejandro Abdelnur commented on MAPREDUCE-3479:
-----------------------------------------------

+1
                
> JobClient#getJob cannot find local jobs
> ---------------------------------------
>
>                 Key: MAPREDUCE-3479
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3479
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.23.0
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: MAPREDUCE-3479.patch, MAPREDUCE-3479.patch
>
>
> The problem is that JobClient#submitJob doesn't pass the Cluster object to Job for the submission process, which means that two Cluster objects and two LocalJobRunner objects are created. LocalJobRunner keeps an instance map of job IDs to Jobs, and when JobClient#getJob is called the LocalJobRunner with the unpopulated map is used which results in the job not being found.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira