[
https://issues.apache.org/jira/browse/YUNIKORN-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887765#comment-17887765
]
Damon Cortesi commented on YUNIKORN-2895:
-----------------------------------------
Also experiencing this after upgrading 1.5.2 to 1.6.0.
The first time it happened, the scheduler had error logs about orphan
applications. The second time, the scheduler still reports as healthy, but
applications don't get scheduled.
{{Request '016df77b-121e-4e22-ab9b-7ae64485e2d2' does not fit in queue
'root.<redacted>' (requested map[memory:2550136832 pods:1 vcore:1000],
available map[ephemeral-storage:891547735818 memory:133673287680 pods:1614
vcore:-137500[])}}
This is on a very low volume test cluster, so let me know if I can help provide
any info.
> Don't add duplicated allocation to node when the allocation ask fails
> ---------------------------------------------------------------------
>
> Key: YUNIKORN-2895
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2895
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Critical
>
> When i try to revisit the new update allocation logic, the potential
> duplicated allocation to node will happen if the allocation already
> allocated. And we try to add the allocation to the node again and don't
> revert it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
