You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Janos Makai (Jira)" <ji...@apache.org> on 2022/12/01 14:21:00 UTC
[jira] [Created] (OOZIE-3681) Revise yarn.app and mapreduce property overrides in Oozie
Janos Makai created OOZIE-3681:
----------------------------------
Summary: Revise yarn.app and mapreduce property overrides in Oozie
Key: OOZIE-3681
URL: https://issues.apache.org/jira/browse/OOZIE-3681
Project: Oozie
Issue Type: Improvement
Affects Versions: 5.2.1
Reporter: Janos Makai
Assignee: Janos Makai
According to the following documentation
[https://hadoop.apache.org/docs/r3.1.2/hadoop-yarn/hadoop-yarn-site/ResourceModel.html]
oozie.launcher.override.memory.mb and oozie.launcher.override.vcores are outdated so the goal is to extend them with currently accepted property keys.
The current keys should be in the beginning of the list to have the highest priority. Legacy overrides need to at end of the lists: oozie.launcher.mapreduce.map.memory.mb & oozie.launcher.mapreduce.map.cpu.vcores & oozie.launcher.mapreduce.map.java.opts
The old keys should *not* be deleted to preserve backward compatibility of Oozie and workflow configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)