[Docs] Document that "oozie.launcher.mapred.child.java.opts" prop. in a
workflow will not propagate to sub-workflows.
---------------------------------------------------------------------------------------------------------------------
Key: OOZIE-619
URL: https://issues.apache.org/jira/browse/OOZIE-619
Project: Oozie
Issue Type: Improvement
Reporter: Harsh J
When you have oozie.launcher.mapred.child.java.opts defined in a job.properties
and use it to submit a workflow that carries subworkflows that launch
single-JVM actions as well, the settings does not propagate down to them. Not
even with <propagate-configuration>. This is cause the config is treated to be
a meta one, and is applied only to the master.
To instead have it do, one would have to inject special configuration elements
like:
In job.properties:
oozieLauncherJVMOpts=-Xmx1g
In workflow.xml:
...
<sub-workflow>
..
<configuration>
...
<property>
<name>oozie.launcher.mapred.child.java.opts</name>
<value>${oozieLauncherJVMOpts}</value>
</property>
</configuration>
We should document this limitation.
Props to Patrick Angeles for finding this.
--
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
