You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/04/30 18:23:00 UTC

[jira] [Commented] (FLINK-9277) Reduce noisiness of SlotPool logging

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

Chesnay Schepler commented on FLINK-9277:
-----------------------------------------

Kind of a duplicate of FLINK-9215. In this [PR|https://github.com/apache/flink/pull/5879] we've been thinking of adding a separate exception class used for the expected life-cycle of resources, which doesn't print a stacktrace.

> Reduce noisiness of SlotPool logging
> ------------------------------------
>
>                 Key: FLINK-9277
>                 URL: https://issues.apache.org/jira/browse/FLINK-9277
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination
>    Affects Versions: 1.5.0
>            Reporter: Stephan Ewen
>            Assignee: Till Rohrmann
>            Priority: Critical
>
> The slot pool logs a vary large amount of stack traces with meaningless exceptions like {code}
> org.apache.flink.util.FlinkException: Release multi task slot because all children have been released.
> {code}
> This makes log parsing very hard.
> For an example, see this log: https://gist.githubusercontent.com/GJL/3b109db48734ff40103f47d04fc54bd3/raw/e3afc0ec3f452bad681e388016bcf799bba56f10/gistfile1.txt



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