[
https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702979#comment-15702979
]
Rohini Palaniswamy commented on OOZIE-2687:
-------------------------------------------
+1 for the idea. Users are always confused about what is the action setting and
what is the launcher setting. This can simplify it.
For env and memory (container size memory.mb), it will probably be better to
keep it simple and mirror the value of the hadoop settings exactly. Makes it
easy to copy-paste between the settings making migration easier and also
internally transfer them to hadoop configuration in the code during job
submission.
For eg:
{code}
<memory>1536</memory>
<java-opts>-Xmx1024M -Dsome.property=true -XX:+RandomJVMSwitch</java-opts>
<env>JYTHON_PATH=./jython:LD_LIBRARY_PATH=./lib</env>
{code}
> OYA: Figure out how to handle MR-specific properties
> ----------------------------------------------------
>
> Key: OOZIE-2687
> URL: https://issues.apache.org/jira/browse/OOZIE-2687
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Peter Cseh
>
> It was possible to manipulate the MapperLauncher's environment through
> properties like:
> # mapreduce.map.memory.mb
> # mapreduce.map.cpu.vcores
> # mapred.child.env
> # mapred.child.java.opts
> # mapred.job.queue.name - ability to set launcher queue
> E.g. We were using mapred.child.env to pass SPARK_HOME to the LauncherMapper
> and make PySpark work.
> Fixing OOZIE-2596 added a hack. We should decide how we support or break
> compatibility and how we allow the manipulation of the Launcher environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
