[
https://issues.apache.org/jira/browse/YUNIKORN-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-2311.
------------------------------------
Fix Version/s: 1.5.0
Resolution: Fixed
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
