[
https://issues.apache.org/jira/browse/FLINK-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904680#comment-15904680
]
Luke Hutchison commented on FLINK-6019:
---------------------------------------
Also, these messages do not respond to setting the logger to send to stderr
rather than stdout, e.g. using
log4j.appender.stdout.Target=System.err
(other log messages do respond to this change to use stderre, and they display
the correct loglevel, e.g. "INFO"/"WARN")
i.e. it seems that there are two logger systems running: the one that writes
through log4j, respecting its settings, and whatever is writing the log entries
above.
> Some log4j messages do not have a loglevel field set, so they can't be
> suppressed
> ---------------------------------------------------------------------------------
>
> Key: FLINK-6019
> URL: https://issues.apache.org/jira/browse/FLINK-6019
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.0
> Environment: Linux
> Reporter: Luke Hutchison
>
> Some of the log messages do not appear to have a loglevel value set, so they
> can't be suppressed by setting the log4j level to WARN. There's this line at
> the beginning which doesn't even have a timestamp:
> Connected to JobManager at Actor[akka://flink/user/jobmanager_1#1844933939]
> And then there are numerous lines like this, missing an "INFO" field:
> 03/10/2017 00:01:14 Job execution switched to status RUNNING.
> 03/10/2017 00:01:14 DataSource (at readTable(DBTableReader.java:165)
> (org.apache.flink.api.java.io.PojoCsvInputFormat))(1/8) switched to SCHEDULED
> 03/10/2017 00:01:14 DataSink (count())(1/8) switched to SCHEDULED
> 03/10/2017 00:01:14 DataSink (count())(3/8) switched to DEPLOYING
> 03/10/2017 00:01:15 DataSink (count())(3/8) switched to RUNNING
> 03/10/2017 00:01:17 DataSink (count())(6/8) switched to FINISHED
> 03/10/2017 00:01:17 DataSource (at readTable(DBTableReader.java:165)
> (org.apache.flink.api.java.io.PojoCsvInputFormat))(6/8) switched to FINISHED
> 03/10/2017 00:01:17 Job execution switched to status FINISHED.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
