[
https://issues.apache.org/jira/browse/MAPREDUCE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168618#comment-13168618
]
Hadoop QA commented on MAPREDUCE-3387:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507216/MR-3387.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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/1434//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1434//console
This message is automatically generated.
> A tracking URL of N/A before the app master is launched breaks oozie
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3387
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3387
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: MR-3387.txt
>
>
> When oozie launches a map/reduce job it retrieves the tracking URL of that
> job to display in its own UI. Previously this tracking URL did not change
> except when the job completed. Currently the URL starts out as N/A and then
> changes to the real URL once the AppMaster launches. This breaks oozie, as
> oozie expects to be able to get that information quickly and get back to
> processing other requests.
> Because the web app proxy is now available we can maintain backwards
> compatibility by instead of returning N/A we can return the URL of the proxy
> for that application. This relies on the fact that the application master's
> UI will display the correct thing for the URI http://<host>:<port>/, which MR
> and others now do.
--
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
