[ https://issues.apache.org/jira/browse/YUNIKORN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-2030. --------------------------------------------- Fix Version/s: 1.5.0 Resolution: Fixed change committed and cherry-picked into branch-1.5 thank you for the analysis and change. > Need to check headroom when trying other nodes for reserved allocations > ----------------------------------------------------------------------- > > Key: YUNIKORN-2030 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2030 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler > Reporter: Yongjun Zhang > Assignee: Yongjun Zhang > Priority: Blocker > Labels: pull-request-available > Fix For: 1.5.0 > > > As reported in YUNIKORN-1996, we are seeing many messages like below from > time to time: > {code:java} > WARN objects/application.go:1504 queue update failed unexpectedly > {“error”: “allocation (map[memory:37580963840 pods:1 vcore:2000]) puts > queue ‘root.test-queue’ over maximum allocation (map[memory:3300011278336 > vcore:390584]), current usage (map[memory:3291983380480 pods:91 > vcore:186000])“}{code} > Restarting Yunikorn helps stoppinging it. Creating this Jira to investigate > why it happened, because it's not supposed to happen as we check if there is > enough resource headroom before calling > > {code:java} > func (sa *Application) tryNode(node *Node, ask *AllocationAsk) *Allocation > {code} > which printed the above message, and only call it when there is enough > headroom. > There maybe a bug in headroom checking? > -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org