You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org> on 2012/03/28 18:53:25 UTC

[jira] [Commented] (FLUME-1073) Default Log4j configuration file should have a rolling policy

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

Arvind Prabhakar commented on FLUME-1073:
-----------------------------------------

Suggested configuration:

{code}
log4j.rootLogger=INFO,LOGFILE
log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.MaxFileSize=10MB
log4j.appender.LOGFILE.MaxBackupIndex=10
log4j.appender.LOGFILE.File=${log.dir}/${log.file}
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n
{code}
                
> Default Log4j configuration file should have a rolling policy
> -------------------------------------------------------------
>
>                 Key: FLUME-1073
>                 URL: https://issues.apache.org/jira/browse/FLUME-1073
>             Project: Flume
>          Issue Type: Task
>    Affects Versions: v1.1.0
>            Reporter: Arvind Prabhakar
>             Fix For: v1.2.0
>
>
> Flume Agents are expected to run for indefinite amount of time and will likely generate a lot of information via it's logs. As such, we need to have a log rolling policy in place to ensure that the system does not run out of disk space due to the log file sizes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira