[
https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208028#comment-13208028
]
Eric Payne commented on MAPREDUCE-3856:
---------------------------------------
I ran a basic mapred program. The program schedules multilple mapred jobs one
after another and prints the tracking ID.
The tracking ID comes out to be the same for all the jobs submitted.
Submit the following pseudo code in a loop and the tracking URL will always be
the same:
{noformat}
// Loop 1 to 10: {
job = new Job(conf, "tracking url" + i);
// ... set up job params ...
job.submit();
System.out.println(job.getJobID() + " : " + job.getTrackingURL());
job.waitForCompletion(true);
// End Loop }
{noformat}
The above will print out something similar to:
{noformat}
job_CLUSTERID_0001 : http://HOST:PORT/proxy/application_CLUSTERID_0001/
job_CLUSTERID_0002 : http://HOST:PORT/proxy/application_CLUSTERID_0001/
...
job_CLUSTERID_0010 : http://HOST:PORT/proxy/application_CLUSTERID_0001/
{noformat}
> 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
>
> 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
