[
https://issues.apache.org/jira/browse/FLINK-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991926#comment-15991926
]
Luke Hutchison commented on FLINK-6019:
---------------------------------------
[~StephanEwen] No, the lines I am talking about do not appear in the log, that
is the whole problem.
See the example below -- the first four lines are in the log (which is also
dumped to stderr), the remaining lines are sent to stdout, and are not sent to
the log:
{noformat}
2017-05-01 17:46:45 INFO Main:181 - RentLogic building score calculator
2017-05-01 17:46:45 INFO Main:127 - Removing temp dir:
/tmp/RentLogic-80019139385321
2017-05-01 17:46:45 INFO Main:147 - Freed /tmp/RentLogic-80019139385321 (0
bytes)
2017-05-01 17:46:47 INFO Main:80 - Reading problem severity score spreadsheet
Connected to JobManager at Actor[akka://flink/user/jobmanager_1#-1367532263]
05/01/2017 17:46:49 Job execution switched to status RUNNING.
05/01/2017 17:46:49 DataSource (read table vowner_building)(1/16) switched
to SCHEDULED
05/01/2017 17:46:49 DataSource (read table vowner_building)(1/16) switched
to DEPLOYING
05/01/2017 17:46:49 DataSource (read table vowner_building)(2/16) switched
to SCHEDULED
05/01/2017 17:46:49 DataSource (read table vowner_building)(2/16) switched
to DEPLOYING
05/01/2017 17:46:49 DataSource (read table vowner_building)(3/16) switched
to SCHEDULED
05/01/2017 17:46:49 DataSource (read table vowner_building)(3/16) switched
to DEPLOYING
05/01/2017 17:46:49 DataSource (read table vowner_building)(4/16) switched
to SCHEDULED
[...]
{noformat}
Calling {{executionConfig.disableSysoutLogging();}} does in fact disable the
additional "Connected to" and "switched to" lines (the Akka log lines), thanks
for the tip.
However, these Akka log lines do not appear in the regular log. What I want to
do is merge these two log types together.
The "switched to" Akka log lines are generated here (I'm not sure where the
"Connected to" line comes from):
https://github.com/apache/flink/blob/master/flink-runtime/src/main/scala/org/apache/flink/runtime/messages/ExecutionGraphMessages.scala#L72
> 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:
> {noformat}
> Connected to JobManager at Actor[akka://flink/user/jobmanager_1#1844933939]
> {noformat}
> And then there are numerous lines like this, missing an "INFO" field:
> {noformat}
> 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.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
