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 "liu bin (Jira)" <ji...@apache.org> on 2025/06/20 08:57:00 UTC

[jira] [Updated] (YARN-11828) Non-exclusive resource allocation respect queue's max capacity

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

liu bin updated YARN-11828:
---------------------------
    Description: 
Now when doing non-exclusive resource allocation, queue's max capacity on the partition will be considered to be 100%. In an ideal situation, preemption policy will reclaim resource back when partitoned-resource-request comes back.


But our cluster has not enabled preemption, so a queue may use all resource on the partition and block the partitoned-resource-request of other queues.


In this situation, we hope queue's max capacity will be respect when doing non-exclusive resource allocation.

  was:
Now when doing non-exclusive resource allocation, queue's max capacity on the partition will be considered to be 100%. In an ideal situation, preemption policy will reclaim resource back when partitoned-resource-request comes back.
But our cluster has not enabled preemption, so a queue may use all resource on the partition and block the partitoned-resource-request of other queues.
In this situation, we hope queue's max capacity will be respect when doing non-exclusive resource allocation.


> Non-exclusive resource allocation respect queue's max capacity
> --------------------------------------------------------------
>
>                 Key: YARN-11828
>                 URL: https://issues.apache.org/jira/browse/YARN-11828
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>            Reporter: liu bin
>            Priority: Major
>
> Now when doing non-exclusive resource allocation, queue's max capacity on the partition will be considered to be 100%. In an ideal situation, preemption policy will reclaim resource back when partitoned-resource-request comes back.
> But our cluster has not enabled preemption, so a queue may use all resource on the partition and block the partitoned-resource-request of other queues.
> In this situation, we hope queue's max capacity will be respect when doing non-exclusive resource allocation.



--
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