Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
FLUME-3396 log4j upgrade from 1.x to latest 2.x
-
- Resolved
-
- relates to
-
FLUME-3271 Update User Guide to follow log4j2 upgrade changes
-
- Patch Available
-
- links to