[
https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782092#comment-15782092
]
Ying Zhang commented on YARN-6024:
----------------------------------
Sorry for the confusion, [~leftnoteasy] and [~sunilg] :-)
Yes, it totally makes sense to me, please go ahead.
Here is what I mean anyway:
In 2.7.3, we are comparing:
{code}newTotalWithoutReservedResource (which is like "totalUsed +
newly_required - resourceCouldBeUnreserved") with currentLimitResource{code}
With {code}newTotalWithoutReservedResource <= currentLimitResource{code}, we
are only checking the queue when "queue's available resource >=
newly_required".
In 2.8, we are comparing:
{code}newTotalWithoutReservedResource (which is like "totalUsed -
resourceCouldBeUnreserved") with currentLimitResource{code}
With {code}newTotalWithoutReservedResource < currentLimitResource{code}, we
are checking the queue as long as "queue's available resource > 0".
There is a slightly difference.
> Capacity Scheduler continuous reservation looking doesn't work when queue's
> used+reserved = max
> -----------------------------------------------------------------------------------------------
>
> Key: YARN-6024
> URL: https://issues.apache.org/jira/browse/YARN-6024
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-6024-branch-2.7.001.patch,
> YARN-6024-branch-2.7.001.patch, YARN-6024.001.patch
>
>
> Found one corner case when continuous reservation looking doesn't work:
> When queue's used=max, the queue's capacity check fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
