[
https://issues.apache.org/jira/browse/YARN-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545523#comment-16545523
]
Botong Huang commented on YARN-8536:
------------------------------------
Hi [~aw], backward compatibility is the reason. Lots of set up scripts has
already taken the assumption as described in yarn.cmd comments:
@rem YARN_\{COMMAND}_HEAPSIZE overrides YARN_HEAPSIZE for a given command
@rem eg
YARN_NODEMANAGER_HEAPSIZE sets the heap
@rem size for the
NodeManager. If you set the
@rem heap size in
YARN_\{COMMAND}_OPTS or YARN_OPTS
@rem they take precedence.
I agree it is not necessary, but it is more friendly to legacy scripts.
Shouldn't hurt right? If there's a strong reason against it, then I can skip.
Thanks!
> Add max heap config option for Federation Router
> ------------------------------------------------
>
> Key: YARN-8536
> URL: https://issues.apache.org/jira/browse/YARN-8536
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Minor
> Attachments: YARN-8536.v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
