[
https://issues.apache.org/jira/browse/OOZIE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188226#comment-16188226
]
Peter Cseh commented on OOZIE-2896:
-----------------------------------
The approach looks good to me.
Please make it somewhat configurable, at least give it the ability to turn the
whole thing off.
> Ensure compatibility for existing LauncherMapper settings
> ---------------------------------------------------------
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
> Issue Type: Sub-task
> Affects Versions: 5.0.0
> Reporter: Peter Bacsko
> Assignee: Andras Piros
> Priority: Blocker
>
> 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.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
