[OOZIE-2896] Ensure compatibility for existing LauncherMapper settings

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.0.0
• Fix Version/s: 5.0.0b1
• Assignee: Andras Piros
• Reporter: Peter Bacsko
• Created: 15/May/17 12:02
• Updated: 19/Mar/18 15:37
• Resolved: 27/Oct/17 13:08

Description

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

Issue Links

• is depended upon by: OOZIE-3099 Implement the equivalent of mapreduce.job.acl-view-job and mapreduce.job.acl-modify-job
• is duplicated by: OOZIE-2892 Implement the equivalent of mapred.job.priority
• is duplicated by: OOZIE-2894 Take heartbeat setting from mapred property
• is related to: OOZIE-2600 OYA: Update Documentation
• links to: ReviewBoard link