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

Hudson commented on MAPREDUCE-3856:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #1813 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1813/])
    MAPREDUCE-3856. Instances of RunningJob class givs incorrect job tracking 
urls when mutiple jobs are submitted from same client jvm. (Contributed by Eric 
Payne) (Revision 1245276)

     Result = SUCCESS
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245276
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestMRJobs.java

                
> Instances of RunningJob class givs incorrect job tracking urls when mutiple 
> jobs are submitted from same client jvm.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3856
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3856
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1, 0.23.2
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>            Priority: Critical
>             Fix For: 0.23.2
>
>         Attachments: MAPREDUCE-3856-1.txt
>
>
> When multiple jobs are submitted from the same client JVM, each call to 
> RunningJob.getTrackingURL() always returns the tracking URL from the first 
> job.
> This happens even if the jobs are submitted and the client waits for the job 
> to complete before submitting the subsequent job. Each job runs fine and is 
> definitely a new, unique job, but the call to getTrackingURL() still returns 
> the URL for the first job.

--
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

        

Reply via email to