[
https://issues.apache.org/jira/browse/YARN-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385024#comment-17385024
]
Eric Badger commented on YARN-10860:
------------------------------------
[~zhuqi], thanks for the review and commit! And thanks [~gandras] for the
additional review. Just a reminder that when committing patches you should
attempt to cherry-pick them as far back as you can unless they are risky and/or
unstable. In this case you committed patches to trunk (3.4) and branch-2.10.
However, the trunk patch should also be cherry-picked back to the other active
3.x branches, which are branch-3.3 and branch-3.2. Could you please cherry-pick
the trunk patch to those 2 branches? Thanks!
> Make max container per heartbeat configs refreshable
> ----------------------------------------------------
>
> Key: YARN-10860
> URL: https://issues.apache.org/jira/browse/YARN-10860
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Major
> Fix For: 3.4.0, 2.10.2
>
> Attachments: YARN-10860.001.patch, YARN-10860.branch-2.10.001.patch
>
>
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
> and
> {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
> are currently *not* refreshable configs, but I believe they should be. This
> JIRA is to turn these into refreshable configs, just like
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}}
> is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
