[
https://issues.apache.org/jira/browse/OOZIE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636937#comment-13636937
]
Robert Kanter commented on OOZIE-1335:
--------------------------------------
I don't think that's a good way because if the user points Oozie at
/etc/hadoop/conf/core-site.xml (i.e. they're actual hadoop install), then we'd
lose the uber mode property.
Instead, we should have the JavaActionExecutor (or similar) set the uber mode
property to true by default; unless the user sets it to false in their WF. We
can also have a setting in oozie-site to disable setting it as the default.
> The launcher job should use uber mode in Hadoop 2 by default
> ------------------------------------------------------------
>
> Key: OOZIE-1335
> URL: https://issues.apache.org/jira/browse/OOZIE-1335
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
>
> In theory, running the launcher job in Hadoop 2's uber mode should make the
> overall action time faster because we don't need to launch as many JVMs.
> I tested this out on a few of the examples in a VM, and it seems to save
> about 10 - 50 seconds per action. While my testing wasn't scientific and was
> only on a single VM, setting the launcher job to run in uber mode by default
> is such a trivial change and should at least not make it slower that I think
> we should do it.
--
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
