[
https://issues.apache.org/jira/browse/OOZIE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026650#comment-16026650
]
Rohini Palaniswamy commented on OOZIE-2896:
-------------------------------------------
Most common ones specified for launcher (prefixed with oozie.launcher. ) are
mapreduce.job.queuename
mapreduce.map.memory.mb
mapreduce.map.java.opts
mapreduce.map.env
mapreduce.job.acl-view-job
mapreduce.job.acl-modfy-job
mapred.job.priority
mapreduce.task.classpath.user.precedence
mapreduce.job.classloader and mapreduce.job.classloader.system.classes
mapreduce.job.hdfs-servers
fs.permissions.umask-mode
dfs.umask (different way of specifying than fs.permissions.umask-mode)
// Since it is running in uber mode, many do configure AM memory settings
directly
yarn.app.mapreduce.am.resource.mb
yarn.app.mapreduce.am.command-opts
yarn.app.mapreduce.am.env
I am just specifying one version of the setting. Deprecated mapred and dfs
equivalent settings are also used. Usually it is taken care by the config
deprecation code and you could just refer by one setting.
Have asked [~satishsaley] to do a git search and find if there are others.
> Ensure compatibility for existing LauncherMapper settings
> ---------------------------------------------------------
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Peter Bacsko
>
> There are a couple of LauncherMapper settings that we should support for
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}},
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since
> there are many of them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
