[
https://issues.apache.org/jira/browse/FLUME-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237803#comment-16237803
]
ASF GitHub Bot commented on FLUME-2050:
---------------------------------------
GitHub user rgoers opened a pull request:
https://github.com/apache/flume/pull/181
FLUME-2050 Upgrade to Log4j 2
This PR removes the use of log4j 1.x from Flume.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/flume flume-2050
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flume/pull/181.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #181
----
commit 140ea5d2808b7f6fce496e5e2d175821f302f25b
Author: Ralph Goers <rgo...@nextiva.com>
Date: 2017-11-03T06:01:58Z
FLUME-2050 Upgrade to Log4j 2
----
> 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
> 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)
