[ 
https://issues.apache.org/jira/browse/OOZIE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189031#comment-16189031
 ] 

Rohini Palaniswamy commented on OOZIE-2896:
-------------------------------------------

bq. for properties within the same group, where the user has defined at least 
two different properties, emit an ERROR log stating that the user has inserted 
contradictory parameter values, and die. 
   Should not error out for these cases. Just need to keep current behavior as 
is which does not fail for any of the scenarios mentioned.
    -  Map/Reduce specific settings have priority over generic child ones. For 
eg: mapred.map.child.env has precedence over mapred.child.env.
    - If both new and deprecated setting is specified last one takes precedence
    - admin settings are prepended to regular settings. For eg:  
yarn.app.mapreduce.am.admin-command-opts and yarn.app.mapreduce.am.command-opts 
both are applied when starting jvm. If there is a conflict, 
yarn.app.mapreduce.am.command-opts will take precedence because it comes last.

> 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)

Reply via email to