You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2021/07/30 18:22:00 UTC

[jira] [Resolved] (YUNIKORN-770) Remove unnecessary DEBUG log while removing a pod from the cache

     [ https://issues.apache.org/jira/browse/YUNIKORN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Weiwei Yang resolved YUNIKORN-770.
----------------------------------
    Fix Version/s: 1.0.0
       Resolution: Fixed

> Remove unnecessary DEBUG log while removing a pod from the cache
> ----------------------------------------------------------------
>
>                 Key: YUNIKORN-770
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-770
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>
> {code:go}
> 	n, ok := cache.nodesMap[pod.Spec.NodeName]
> 	if !ok {
> 		return fmt.Errorf("node %v is not found", pod.Spec.NodeName)
> 	}
> 	if err := n.RemovePod(pod); err != nil {
> 		return err
> 	}
> {code}
> It can causes DEBUG log("node  is not found") if node name is an empty string. For example: the pod status is updated (according to outstanding requests) before it is assumed to be run on a node.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org