[
https://issues.apache.org/jira/browse/FLUME-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Percy updated FLUME-1073:
------------------------------
Release Note: If the user keeps the default log4j.properties in place,
flume now logs to flume.log instead of stdout. This can be overridden on the
command line by specifying an argument similar to the following:
-Dflume.root.logger=DEBUG,console
Status: Patch Available (was: Open)
> 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
>
> Attachments: FLUME-1073-2.patch
>
>
> 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
