[
https://issues.apache.org/jira/browse/YARN-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023444#comment-18023444
]
ASF GitHub Bot commented on YARN-11828:
---------------------------------------
github-actions[bot] commented on PR #7753:
URL: https://github.com/apache/hadoop/pull/7753#issuecomment-3344446402
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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: [email protected]
For additional commands, e-mail: [email protected]
