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 2017/02/23 15:17:44 UTC

[jira] [Commented] (FLINK-5895) Reduce logging aggressiveness of FileSystemSafetyNet

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

Stephan Ewen commented on FLINK-5895:
-------------------------------------

This is a good example of why logging inside utility methods is often tricky. It is better to log in the classes that invoke the utilities, because they have the context to see whether and on what level the operation should be logged.

> Reduce logging aggressiveness of FileSystemSafetyNet
> ----------------------------------------------------
>
>                 Key: FLINK-5895
>                 URL: https://issues.apache.org/jira/browse/FLINK-5895
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>    Affects Versions: 1.2.0
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.3.0, 1.2.1
>
>
> The {{FileSystemSafetyNet}} logs on info level every time it is created and destroyed. This causes a log flood from the async checkpoint thread, which starts and stops that safety net very often.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)