[ https://issues.apache.org/jira/browse/FLINK-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195667#comment-17195667 ]
Jörn Kottmann commented on FLINK-8357: -------------------------------------- Kafka is using hourly rotating logs without a max size. This is probably a good solution for my particular use case with EMR. In general this seems to be more complicated since Flink supports multiple deployment targets and it is probably hard to provide a good default for all of them. Different targets could be addressed with different log4j2 configurations if required, writing also directly to stdout / stderr could be good for some of them. Let me propose to implement hourly rotating logs with a fixed number of files for 7 days. If storage space for the logs is a concern additional compression for the rotated files could be enabled (or be commented out for user adjustment). > enable rolling in default log settings > -------------------------------------- > > Key: FLINK-8357 > URL: https://issues.apache.org/jira/browse/FLINK-8357 > Project: Flink > Issue Type: Improvement > Components: Build System, Deployment / Scripts > Reporter: Mingmin Xu > Assignee: Jörn Kottmann > Priority: Major > Labels: usability > Time Spent: 10m > Remaining Estimate: 0h > > The release packages uses {{org.apache.log4j.FileAppender}} for log4j and > {{ch.qos.logback.core.FileAppender}} for logback, which could results in very > large log files. > For most cases, if not all, we need to enable rotation in a production > cluster, and I suppose it's a good idea to make rotation as default. -- This message was sent by Atlassian Jira (v8.3.4#803005)