You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/03/14 04:47:00 UTC
[jira] [Commented] (YUNIKORN-1091) node capacity update not updated in cache
[ https://issues.apache.org/jira/browse/YUNIKORN-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505989#comment-17505989 ]
Wilfred Spiegelenburg commented on YUNIKORN-1091:
-------------------------------------------------
As you mentioned in the [PR for YUNIKORN-1090|https://github.com/apache/incubator-yunikorn-k8shim/pull/380#discussion_r824543728] I think this has been solved as part of that change.
If so we should close this one as "implemented". I linked the jiras
> 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
>
> {{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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org