[
https://issues.apache.org/jira/browse/OOZIE-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643274#comment-17643274
]
Janos Makai commented on OOZIE-3681:
------------------------------------
[~dionusos] thanks for the review, based on your suggestion I've checked the
valid Hadoop 2.6.0 configuration properties, but they do not contain the ones
that are being added with in this change, as unfortunately they're Hadoop 3
related.
Therefore I'm closing this ticket.
> 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
> Priority: Major
> Attachments: OOZIE-3681-001.patch
>
>
> 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)
