[
https://issues.apache.org/jira/browse/FLUME-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352482#comment-16352482
]
ASF subversion and git services commented on FLUME-2050:
--------------------------------------------------------
Commit 69c66efefdcd74904986f2727bdf0d52dd9a75e5 in flume's branch
refs/heads/trunk from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=69c66ef ]
FLUME-2050. Upgrade to Log4j 2.10.0
This closes #181
Reviewers: Ferenc Szabo
(Ralph Goers via Denes Arvay)
> 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
> Priority: Major
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
