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 2020/04/14 07:38:00 UTC

[jira] [Commented] (YUNIKORN-25) Logging improvements

    [ https://issues.apache.org/jira/browse/YUNIKORN-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082949#comment-17082949 ] 

Wilfred Spiegelenburg commented on YUNIKORN-25:
-----------------------------------------------

k8shim changes have been committed.

Most, if not all, of the changes in the core have been superseded with changes from a different PR. [~wwei] can you check that PR #124 for the core and let me know what we are going to do with that.

> Logging improvements
> --------------------
>
>                 Key: YUNIKORN-25
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-25
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: shim - kubernetes
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Weiwei Yang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Lots of logs were from predicator and some from the core scheduling process. We need to fix this. I can see it goes to hundreds of MBs after running for a while when there are some pending requests.
> a change has already been made in PR [apache/incubator-yunikorn-k8shim#54|https://github.com/apache/incubator-yunikorn-k8shim/pull/54] , scheduling-task logs can be printed repeatedly to alleviate the issue



--
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