You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Edward Sargisson (JIRA)" <ji...@apache.org> on 2013/05/29 01:48:19 UTC
[jira] [Updated] (FLUME-2050) Upgrade to log4j2 (when GA)
[ https://issues.apache.org/jira/browse/FLUME-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Sargisson updated FLUME-2050:
------------------------------------
Attachment: FLUME-2050.patch
Patch for Flume using log4j2. Largest area of change was TestSyslogUdpSource. Note that we should wait for log4j2 to go to GA before doing this upgrade and thus I will not create a review board for it yet. I'm uploading this patch so that it's ready to go and in case somebody needs it.
> Upgrade to log4j2 (when GA)
> ---------------------------
>
> Key: FLUME-2050
> URL: https://issues.apache.org/jira/browse/FLUME-2050
> Project: Flume
> Issue Type: Improvement
> Reporter: Edward Sargisson
> Attachments: FLUME-2050.patch
>
>
> Log4j1 is being abandoned in favour of log4j2. Log4j2, by all that I've seen, has better concurrency handling and the Log4j2 FlumeAppender is nice (easily configurable, 3 different styles of agents).
> Log4j1 has a concurrency defect which means that rolling over a log file into a directory for the Flume spool directory source will not be reliable. Log4j2 has fixed this.
> Alternatively the log4j2 FlumeAppender may allow Flume to log its own logs via itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira