You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2018/03/07 20:57:00 UTC

[jira] [Resolved] (FLINK-8877) Configure Kryo's log level based on Flink's log level

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

Stephan Ewen resolved FLINK-8877.
---------------------------------
    Resolution: Fixed

Fixed in
  - 1.5.0 via b0418b41f8fa02d3217b760c5bdfcdd7efdc1eac
  - 1.6.0 via 06110d27d5fcbf939610e2adc780e7ad1c467f6f

> Configure Kryo's log level based on Flink's log level
> -----------------------------------------------------
>
>                 Key: FLINK-8877
>                 URL: https://issues.apache.org/jira/browse/FLINK-8877
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>             Fix For: 1.5.0, 1.6.0
>
>
> Kryo uses its embedded MinLog for logging.
> When Flink is set to trace, Kryo should be set to trace as well. Other log levels should not be uses, as even debug logging in Kryo results in excessive logging.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)