[
https://issues.apache.org/jira/browse/YARN-8509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zian Chen updated YARN-8509:
----------------------------
Description:
In LeafQueue#getTotalPendingResourcesConsideringUserLimit, we calculate total
pending resource based on user-limit percent and user-limit factor which will
cap pending resource for each user to the minimum of user-limit pending and
actual pending. This will prevent queue from taking more pending resource to
achieve queue balance after all queue satisfied with its ideal allocation.
We need to change the logic to let queue pending can reach at most
(Queue_max_capacity - Queue_used_capacity).
was:In LeafQueue#getTotalPendingResourcesConsideringUserLimit, we calculate
total pending resource based on user-limit percent and user-limit factor which
will cap pending resource for each user to the minimum of user-limit pending
and actual pending. This will prevent queue from taking more pending resource
and
> Fix UserLimit calculation for preemption to balance scenario after queue
> satisfied
> ------------------------------------------------------------------------------------
>
> Key: YARN-8509
> URL: https://issues.apache.org/jira/browse/YARN-8509
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Zian Chen
> Assignee: Zian Chen
> Priority: Major
>
> In LeafQueue#getTotalPendingResourcesConsideringUserLimit, we calculate total
> pending resource based on user-limit percent and user-limit factor which will
> cap pending resource for each user to the minimum of user-limit pending and
> actual pending. This will prevent queue from taking more pending resource to
> achieve queue balance after all queue satisfied with its ideal allocation.
>
> We need to change the logic to let queue pending can reach at most
> (Queue_max_capacity - Queue_used_capacity).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]