[jira] [Commented] (FLINK-7722) MiniCluster does not appear to honor Log4j settings

["Stephan Ewen (JIRA)" <ji...@apache.org>]

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

Stephan Ewen commented on FLINK-7722:
-------------------------------------

I think we may want to make "not sysout logging" the default and explicitly enable it on the CLI client.
It tends to confuse...

> MiniCluster does not appear to honor Log4j settings
> ---------------------------------------------------
>
>                 Key: FLINK-7722
>                 URL: https://issues.apache.org/jira/browse/FLINK-7722
>             Project: Flink
>          Issue Type: Bug
>          Components: Local Runtime
>    Affects Versions: 1.3.2
>            Reporter: Elias Levy
>            Priority: Minor
>
> When executing a job from the command line for testing, it will output logs like:
> {noformat}
> Connected to JobManager at Actor[akka://flink/user/jobmanager_1#1337544104] with leader session id 59dd0d9c-938e-4e79-a0eb-709c5cf73014.
> 09/27/2017 13:15:13	Job execution switched to status RUNNING.
> 09/27/2017 13:15:13	Source: Custom File Source(1/1) switched to SCHEDULED 
> 09/27/2017 13:15:13	Source: Collect
> {noformat}
> It will do so even if the log4j.properties file contains:
> {code}
> log4j.rootLogger=ERROR, stdout
> log4j.logger.org.apache.flink=ERROR
> log4j.logger.akka=ERROR
> log4j.logger.org.apache.kafka=ERROR
> log4j.logger.org.apache.hadoop=ERROR
> log4j.logger.org.apache.zookeeper=ERROR
> {code}
> It seems that the MiniCluster does not honor Log4j settings, or at least that is my guess.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)