[
https://issues.apache.org/jira/browse/YUNIKORN-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909010#comment-17909010
]
Michael Chu commented on YUNIKORN-2907:
---------------------------------------
Hi [~wilfreds] thanks for the detailed guidance! It's clear to me. I have one
remaining question, should the last problem you mentioned be done as part of
this PR?
> Queue config processing log spew
> --------------------------------
>
> Key: YUNIKORN-2907
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2907
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - common
> Reporter: Wilfred Spiegelenburg
> Assignee: Michael Chu
> Priority: Major
> Labels: pull-request-available
>
> During configuration updates a shadow queue structure is build based on the
> new configuration. The shadow structure is then walked and compared to the
> existing queue structure. Actions are taken based on the existing queue
> structure: add or remove of queues that exist in new or existing structure.
> Update if differences are found between queues that exist in new and existing
> structures.
> During the build of the shadow structure queue creations are logged. This
> logs the creation of the whole queue structure. The logs do not make clear
> the queues are not really added but that it is the shadow structure being
> created. In case of large queue structures this causes a log spew, and makes
> the log difficult to read.
> The actions taken based on the comparison are logged clearly.
> We need to be able to distinguish between a real create and one for the
> shadow create in the log. The same code is executed when we create the "real"
> queue.
> The creation of the shadow queue structure should not log, log only at debug
> level and or log with a clear message that it is the shadow structure
> creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
