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

[email protected] commented on FLUME-1073:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4565/
-----------------------------------------------------------

(Updated 2012-03-30 21:38:31.640395)


Review request for Flume.


Changes
-------

Updated patch so that we can now specify -Dflume.root.logger=DEBUG,console when 
invoking Flume on the command line, which overrides the log4j.rootLogger. I 
think that's a reasonable thing to ask of developers. At the same time, "out of 
the box", Flume has logging that is sane for a production environment.


Summary
-------

Simple patch to default to a reasonably-configured rolling file appender.


This addresses bug FLUME-1073.
    https://issues.apache.org/jira/browse/FLUME-1073


Diffs (updated)
-----

  bin/flume-ng a31f171 
  conf/log4j.properties 3dcffd4 

Diff: https://reviews.apache.org/r/4565/diff


Testing
-------

Did some manual testing, looks fine to me.


Thanks,

Mike


                
> 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
>            Assignee: Mike Percy
>             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

        

Reply via email to