You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/12/01 09:51:59 UTC

[jira] [Closed] (FLINK-5207) Decrease HadoopFileSystem logging

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

Ufuk Celebi closed FLINK-5207.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.4
                   1.2.0

Fixed in bf859e7 (master), 28e44e7 (release-1.1).

> Decrease HadoopFileSystem logging
> ---------------------------------
>
>                 Key: FLINK-5207
>                 URL: https://issues.apache.org/jira/browse/FLINK-5207
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Ufuk Celebi
>             Fix For: 1.2.0, 1.1.4
>
>
> HadoopFileSystem logging is very noisy when trying to get the Hadoop configuration, which happens for every HadoopFileSystem. This happens for example when a checkpoint is written to HDFS in case of HA.
> 1) Two log messages relate to the user config:
> {code}
> final String hdfsDefaultPath = GlobalConfiguration.getString(ConfigConstants.HDFS_DEFAULT_CONFIG, null);
> 		if (hdfsDefaultPath != null) {
> 			retConf.addResource(new org.apache.hadoop.fs.Path(hdfsDefaultPath));
> 		} else {
> 			LOG.debug("Cannot find hdfs-default configuration file");
> 		}
> {code}
> Since this is reflected in the logged configuration properties, it is mostly unnecessary to log over and over again. Therefore I propose to go with TRACE.
> (2) Two log messages relate to the default config files of Hadoop. There I would change the debug message to happen only when they are *not* found. If it is still too noisy, we could completely remove it or decrease to TRACE at another time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)