You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Eric Payne (Created) (JIRA)" <ji...@apache.org> on 2012/02/13 17:34:59 UTC
[jira] [Created] (MAPREDUCE-3856) Instances of RunningJob class
givs incorrect job tracking urls when mutiple jobs are submitted from same
client jvm.
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