Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.4.2
-
None
-
None
Description
Based on this https://issues.apache.org/jira/browse/FLINK-9471 we are forced to keep INFO for packages like org.apache.flink.runtime.executiongraph, despite their verbosity. An attempt to roll these logs, so that they do not fill the disk, leads to them not showing up in the UI (JobManager logs or TaskManager logs). The log4j.properties attempted is below.
log4j.rootLogger=WARN, SizeBasedRollingFile
log4j.logger.org.apache.flink=INFO
- Suppress the irrelevant (wrong) warnings from the Netty channel handler
log4j.logger.org.apache.flink.shaded.akka.org.jboss.netty.channel.DefaultChannelPipeline=ERROR
log4j.logger.com.myPackage=INFO, DateBasedRollingFile
log4j.appender.SizeBasedRollingFile=org.apache.log4j.RollingFileAppender
log4j.appender.SizeBasedRollingFile.File=${log.file}
log4j.appender.SizeBasedRollingFile.maxFileSize=10000
log4j.appender.SizeBasedRollingFile.maxBackupIndex=10
log4j.appender.SizeBasedRollingFile.layout=org.apache.log4j.PatternLayout
log4j.appender.SizeBasedRollingFile.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %-60c - %m%n
log4j.appender.DateBasedRollingFile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.DateBasedRollingFile.File=${log.file}-application
log4j.appender.DateBasedRollingFile.DatePattern='.'yyyy-MM-dd-HH-mm-ss
log4j.appender.DateBasedRollingFile.layout=org.apache.log4j.PatternLayout
log4j.appender.DateBasedRollingFile.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %-60c - %m%n
Attachments
Issue Links
- duplicates
-
FLINK-13987 Better TM/JM Log Display
- Closed