You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flume.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/02/28 05:12:00 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 ]

Ralph Goers updated FLUME-2050:
-------------------------------
    Fix Version/s: 1.10.0
                       (was: 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
>            Priority: Major
>             Fix For: 1.10.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
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org