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 2020/05/22 23:55:00 UTC
[jira] [Assigned] (YUNIKORN-183) Logging clean up
[ https://issues.apache.org/jira/browse/YUNIKORN-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang reassigned YUNIKORN-183:
------------------------------------
Assignee: Weiwei Yang
> Logging clean up
> ----------------
>
> Key: YUNIKORN-183
> URL: https://issues.apache.org/jira/browse/YUNIKORN-183
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler, shim - kubernetes
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
>
> Today, we are logging too many things at the DEBUG level. That makes the issue tracking super difficult. We need to do some cleanup at some critical paths. A few things, we need to look at
> # Reduce, or minimize the logs at core scheduling cycle (this is going overwhelming)
> # Keep tracking of main things happening, allocation, release, reservation, preservation etc
> this is a parent, we need to create sub tasks for core and shim.
--
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