You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junfan Zhang (Jira)" <ji...@apache.org> on 2022/03/15 04:57:00 UTC
[jira] [Comment Edited] (YARN-11088) Introduce the config to control the AM allocated to non-exclusive nodes
[ https://issues.apache.org/jira/browse/YARN-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506703#comment-17506703 ]
Junfan Zhang edited comment on YARN-11088 at 3/15/22, 4:56 AM:
---------------------------------------------------------------
Could you help check this feature? [~quapaw] [~tdomok].
If OK, please assign to me.
was (Author: zuston):
Could you help check this feature? [~quapaw] [~tdomok]
> Introduce the config to control the AM allocated to non-exclusive nodes
> -----------------------------------------------------------------------
>
> Key: YARN-11088
> URL: https://issues.apache.org/jira/browse/YARN-11088
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Junfan Zhang
> Priority: Major
>
> h4. Why
> Current the implementation of Yarn about AM allocation on non-exclusive nodes is directly to fail fast. I know this aims to keep the stability of job, because the container in non-exclusive nodes will be preempted.
> But Yarn cluster in our internal company exists on-premise NodeManagers and elastic NodeManagers (which is built on K8s). When all the elastic nodemanagers decommission, we hope that the AM can be scheduled to non-exclusive nodes.
> h4. How to support it
> Introduce the new config to control the AM can be allocated to non-exclusive nodes.
> *Feel free to discuss if having any ideas!*
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org