[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210951#comment-13210951 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-0.23-Build #200 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/200/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245842) Result = FAILURE acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245842 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt > 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.0 >Reporter: Eric Payne >Assignee: Eric Payne >Priority: Critical > Fix For: 0.23.1 > > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210960#comment-13210960 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-trunk #994 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/994/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245840) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245840 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt > 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.0 >Reporter: Eric Payne >Assignee: Eric Payne >Priority: Critical > Fix For: 0.23.1 > > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210922#comment-13210922 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-0.23-Build #172 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/172/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245842) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245842 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt > 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.0 >Reporter: Eric Payne >Assignee: Eric Payne >Priority: Critical > Fix For: 0.23.1 > > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210913#comment-13210913 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-trunk #959 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/959/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245840) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245840 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt > 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.0 >Reporter: Eric Payne >Assignee: Eric Payne >Priority: Critical > Fix For: 0.23.1 > > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210794#comment-13210794 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-trunk-Commit #1761 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1761/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245840) Result = ABORTED acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245840 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210795#comment-13210795 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-0.23-Commit #574 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/574/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245842) Result = ABORTED acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245842 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210775#comment-13210775 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-0.23-Commit #558 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/558/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245842) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245842 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210774#comment-13210774 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Common-0.23-Commit #571 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/571/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245842) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245842 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210767#comment-13210767 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-trunk-Commit #1823 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1823/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245840) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245840 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210768#comment-13210768 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Common-trunk-Commit #1749 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1749/]) MAPREDUCE-3856. Committing to 0.23.1. (Revision 1245840) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245840 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210373#comment-13210373 ] Amol Kekre commented on MAPREDUCE-3856: --- We need this in .23.1 > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210305#comment-13210305 ] Eric Payne commented on MAPREDUCE-3856: --- Thanks very much, Sid! > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210271#comment-13210271 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-trunk #993 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/993/]) 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210252#comment-13210252 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-0.23-Build #199 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/199/]) merge MAPREDUCE-3856 from trunk (Revision 1245277) Result = FAILURE sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245277 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210230#comment-13210230 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-trunk #958 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/958/]) 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210217#comment-13210217 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-0.23-Build #171 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/171/]) merge MAPREDUCE-3856 from trunk (Revision 1245277) Result = SUCCESS sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245277 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209980#comment-13209980 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-0.23-Commit #566 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/566/]) merge MAPREDUCE-3856 from trunk (Revision 1245277) Result = ABORTED sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245277 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209974#comment-13209974 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Mapreduce-trunk-Commit #1751 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1751/]) 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 = ABORTED 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209961#comment-13209961 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Common-0.23-Commit #563 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/563/]) merge MAPREDUCE-3856 from trunk (Revision 1245277) Result = SUCCESS sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245277 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209957#comment-13209957 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Hdfs-0.23-Commit #550 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/550/]) merge MAPREDUCE-3856 from trunk (Revision 1245277) Result = SUCCESS sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245277 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java * /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209949#comment-13209949 ] Hudson commented on MAPREDUCE-3856: --- Integrated in Hadoop-Common-trunk-Commit #1739 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1739/]) 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209941#comment-13209941 ] Siddharth Seth commented on MAPREDUCE-3856: --- +1. Looks good. Will commit the patch shortly. > 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 > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208756#comment-13208756 ] Hadoop QA commented on MAPREDUCE-3856: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12514685/MAPREDUCE-3856-1.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1865//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1865//console This message is automatically generated. > 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 > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208694#comment-13208694 ] Eric Payne commented on MAPREDUCE-3856: --- Patch applies the same to both branch-0.23 and trunk. > 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 > 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
[jira] [Commented] (MAPREDUCE-3856) Instances of RunningJob class givs incorrect job tracking urls when mutiple jobs are submitted from same client jvm.
[
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
