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

ASF GitHub Bot commented on FLINK-8357:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/5371
  
    The CI Server reports the following problem below. Apparently the 
configurations cause warnings to be printed. Can you have a look at that?
    
    ```
    Found non-empty .out files:
    log4j:WARN No such property [maxBackupIndex] in 
org.apache.log4j.DailyRollingFileAppender.
    log4j:WARN No such property [maxFileSize] in 
org.apache.log4j.DailyRollingFileAppender.
    log4j:WARN No such property [maxBackupIndex] in 
org.apache.log4j.DailyRollingFileAppender.
    log4j:WARN No such property [maxFileSize] in 
org.apache.log4j.DailyRollingFileAppender.
    One or more tests FAILED.
    ```



> enable rolling in default log settings
> --------------------------------------
>
>                 Key: FLINK-8357
>                 URL: https://issues.apache.org/jira/browse/FLINK-8357
>             Project: Flink
>          Issue Type: Improvement
>          Components: Logging
>            Reporter: Xu Mingmin
>            Assignee: mingleizhang
>            Priority: Major
>             Fix For: 1.5.0
>
>
> 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
(v7.6.3#76005)

Reply via email to