[jira] [Updated] (YARN-11088) Introduce the config to control the AM allocated to non-exclusive nodes

["Shilun Fan (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shilun Fan updated YARN-11088:
------------------------------
          Component/s: capacity scheduler
     Target Version/s: 3.4.0
    Affects Version/s: 3.4.0

> 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
>          Components: capacity scheduler
>    Affects Versions: 3.4.0
>            Reporter: Junfan Zhang
>            Assignee: Junfan Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> 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.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org