Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-335

FlumePersistentManager has high CPU usage

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0-beta8
    • 2.0-beta9
    • Flume Appender
    • None

    Description

      FlumePersistentManager wakes up each time an event is written and checks whether anything should be done. In that is writing logs fairly frequently this results in high CPU usage in the writer thread.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            rgoers Ralph Goers
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment