[
https://issues.apache.org/jira/browse/YARN-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890322#comment-16890322
]
Sunil Govindan commented on YARN-9687:
--------------------------------------
Hi [~Tao Yang]
Thanks for reporting this issue. Yes, we have seen this in few places where
such cases can occur given the combination of resource values. *fitsIn* helps
in such areas. (already we fixed few in preemption modules)
+1 for this patch.
> Queue headroom check may let unacceptable allocation off when using
> DominantResourceCalculator
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-9687
> URL: https://issues.apache.org/jira/browse/YARN-9687
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Major
> Attachments: YARN-9687.001.patch
>
>
> Currently queue headroom check in {{RegularContainerAllocator#checkHeadroom}}
> is using {{Resources#greaterThanOrEqual}} which internally compare resources
> by ratio, when using DominantResourceCalculator, it may let unacceptable
> allocations off in some scenarios.
> For example:
> cluster-resource=<10GB, 10 vcores>
> queue-headroom=<2GB, 4 vcores>
> required-resource=<3GB, 1 vcores>
> In this way, headroom ratio(0.4) is greater than the required ratio(0.3), so
> that allocations will be let off in scheduling process but will always be
> rejected when committing these proposals.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
