[
https://issues.apache.org/jira/browse/YUNIKORN-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-480.
-----------------------------------
Fix Version/s: 0.10
Resolution: Fixed
> root queue max resource gets reset on config load
> -------------------------------------------------
>
> Key: YUNIKORN-480
> URL: https://issues.apache.org/jira/browse/YUNIKORN-480
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 0.10
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.10
>
>
> When updating the configuration the root queue max resource is getting reset
> to {{nil}}. The configuration should never set the root queue resources. On
> creation of the queue this is not a problem as there cannot be any registered
> node. On update we have registered nodes and should thus not clear it out.
> When the max resource gets reset it stops allocation as the scheduler thinks
> there are no nodes registered and nothing can be done.
> Found by the e2e tests as part of the shim dependency change YUNIKORN-475
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
