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 2022/03/02 17:21:00 UTC

[jira] [Resolved] (YUNIKORN-1097) RMProxy DEBUG cannot log event with channel

     [ https://issues.apache.org/jira/browse/YUNIKORN-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg resolved YUNIKORN-1097.
---------------------------------------------
    Fix Version/s: 1.0.0
       Resolution: Fixed

leveraging json annotation to remove channels from being logged.

thank you [~steinsgateted] for your contribution

> RMProxy DEBUG cannot log event with channel
> -------------------------------------------
>
>                 Key: YUNIKORN-1097
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1097
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - common
>    Affects Versions: 1.0.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: ted
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>
> The rmproxy logs:
> {code:java}
> 2022-02-25T15:50:01.371-0600    DEBUG   rmproxy/rmproxy.go:64   enqueue event   {"eventError": "json: unsupported type: chan *rmevent.Result", "currentQueueSize": 0} {code}
> This is caused by the events that contain a channel as it cannot be represented.
> zap.Any prefers not to use reflection and will pick up if the object implements a String method which we can use as a workaround on events that include a channel.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org