Michael Friedmann created LOG4J2-563:
----------------------------------------
Summary: FlumeAppender may cause application to hang if only one
Flume agent is configured
Key: LOG4J2-563
URL: https://issues.apache.org/jira/browse/LOG4J2-563
Project: Log4j 2
Issue Type: Bug
Affects Versions: 2.0-rc1
Reporter: Michael Friedmann
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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
