Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-2050

Upgrade to log4j2 (when GA)

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.10.0
    • 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

        Issue Links

        is duplicated by

        Question - A formal question. Initially added for the Legal JIRA. FLUME-3396 log4j upgrade from 1.x to latest 2.x

        • Major - Major loss of function.
        • Resolved
        relates to

        Documentation - Documentation or Website FLUME-3271 Update User Guide to follow log4j2 upgrade changes

        • Major - Major loss of function.
        • Patch Available
        links to

        Web Link GitHub Pull Request #181

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            ejsarge Edward Sargisson
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment