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 2023/02/08 01:13:00 UTC
[jira] [Assigned] (YUNIKORN-1530) remove log spew in schedulerplugin
[ https://issues.apache.org/jira/browse/YUNIKORN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg reassigned YUNIKORN-1530:
-----------------------------------------------
Assignee: Krishna Birla
> remove log spew in schedulerplugin
> ----------------------------------
>
> Key: YUNIKORN-1530
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1530
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Krishna Birla
> Priority: Major
>
> In the {{yunikorn-k8shim/pkg/schedulerplugin/scheduler_plugin.go}} we log at an Info level each time we get an application that does not contain an applicationID.
> This causes a log spew in large clusters as the plugins can be called for each node logging lots of lines like:
> {code:java}
> 2022-12-01T06:51:19.922Z INFO schedulerplugin/scheduler_plugin.go:140 Skipping pod namespace1/job-27831291-mkv55 in the filter plugin because no applicationID is defined{code}
> This message should either be only logged once, using a local cache to track that the message has been logged already or moved to a Debug level. This applies to both Skipping pod messages in the code.
> We should also fix up the way the messages are created and not use the fmt.Sprintf() call but leverage the proper zap logger as we do for all other messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org