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

FlumeAppender may cause application to hang if only one Flume agent is configured

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-rc1
    • Fix Version/s: 2.0-rc2
    • Component/s: None
    • Labels:
      None

      Description

      If a FlumeAppender is configured with only one Flume agent, when the agent is down, this may cause the application to hang.

      We observed this behavior to happen at specific repeatable points in our application. However, when we reconfigured with multiple Flume agents, the application did not hang - even with all Flume agents being down.

      Looking at the code (i.e. FlumeAvroManager), it appears that you are setting the 'client.type' property to 'default' when one agent is configured, vice 'default_failover' when more than one agent is configured. I recommend that you always set 'client.type' to 'default_failover'. This would be consistent with Flume's documentation and appears to resolve the issue.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mfriedmann Michael Friedmann
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: