[
https://issues.apache.org/jira/browse/YUNIKORN-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg updated YUNIKORN-1091:
--------------------------------------------
Fix Version/s: 1.0.0
> node capacity update not updated in cache
> -----------------------------------------
>
> Key: YUNIKORN-1091
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1091
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Manikandan R
> Priority: Critical
> Fix For: 1.0.0
>
>
> {{ctx.updateNode()}} gets called by the K8s client event handling. This
> updates the two caches using two calls:
> # {{ctx.schedulerCache.UpdateNode()}}
> # {{ctx.nodes.updateNode()}}
> The first call adds the node (type _framework.NodeInfo_) if it does not exist
> and otherwise replaces the entry in the cache with the new info (GOOD)
> The second call adds the node (type _SchedulerNode_) if it does no exist to
> (GOOD). If the node exists it checks for a resource change. The call results
> in a notification of the scheduler core. It does NOT update the secondary
> cache with this change. This leaves the SchedulerNode capacity unchanged and
> out of sync.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
