[
https://issues.apache.org/jira/browse/FLUME-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved FLUME-2050.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
> 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
> Fix For: 1.9.0
>
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)
