[
https://issues.apache.org/jira/browse/OOZIE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651307#comment-13651307
]
Robert Kanter commented on OOZIE-1231:
--------------------------------------
That's been happening a lot recently. Perhaps one of the more recent patches
added in some test that's not exiting properly and leaving something running?
> Provide access to launcher job URL from web console when using Map Reduce
> action
> --------------------------------------------------------------------------------
>
> Key: OOZIE-1231
> URL: https://issues.apache.org/jira/browse/OOZIE-1231
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
> Labels: oozie
> Fix For: trunk
>
> Attachments: OOZIE-1231-v3.patch, OOZIE-1231-v4.patch,
> OOZIE-1231-v6.patch, OOZIE-1231-v7.patch, OOZIE-1231-v8.patch,
> OOZIE-1231-v9.patch, Screen Shot Launcher_Job_URL_tab.png,
> ScreenShot-MapReduceAction-New.png
>
>
> there are applications where custom inputformat used in MR action, and log
> message from the inputformat is written on launcher task log. for debugging
> purpose, users need to check the launcher task log. but currently in MR
> action, oozie automatically swaps external ID, and do not expose the launcher
> ID in web-console. (now only way is to to grep oozie.log). this jira is to
> show launcher job URL on web console when using Map Reduce action
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
