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/05/12 04:52:00 UTC

[jira] [Updated] (YUNIKORN-663) Improve log messages in node.go

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

Weiwei Yang updated YUNIKORN-663:
---------------------------------
    Fix Version/s: 0.11

> Improve log messages in node.go
> -------------------------------
>
>                 Key: YUNIKORN-663
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-663
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: shim - kubernetes
>            Reporter: Kinga Marton
>            Priority: Major
>              Labels: newbie
>             Fix For: 0.11
>
>
> There are some places when the log message did not have any identity information, for example when the occupied resources are set ([https://github.com/apache/incubator-yunikorn-k8shim/blob/master/pkg/cache/node.go#L115)] we log a message that this is happening, but there is no node ID mentioned, so this message in this form is totally useless.
> An another example is when an allocation added: ([https://github.com/apache/incubator-yunikorn-k8shim/blob/master/pkg/cache/node.go#L107)]
> We should revisit this log messages and extend them with some identification related information. At least with the nodeID.
>  



--
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