You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/01/05 17:16:00 UTC
[jira] [Created] (YUNIKORN-2311) Log spew on nil guaranteed / max resources after YUNIKORN-2169
Craig Condit created YUNIKORN-2311:
--------------------------------------
Summary: Log spew on nil guaranteed / max resources after YUNIKORN-2169
Key: YUNIKORN-2311
URL: https://issues.apache.org/jira/browse/YUNIKORN-2311
Project: Apache YuniKorn
Issue Type: Bug
Components: core - scheduler
Reporter: Craig Condit
Assignee: Manikandan R
YUNIKORN-2169 made changes to the processing of queue resources. However, some DEBUG messages related to nil resources were changed to WARN instead. This produces ugly stack traces and should be reverted (all levels >= WARN produce stack traces). DEBUG was appropriate as this is a normal and even frequent condition, as it's common to have queues which have unspecified max or guaranteed resources. Even INFO would be too verbose in this scenario.
--
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