[
https://issues.apache.org/jira/browse/LOG4J2-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-563.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-rc2
I don't see in the Flume documentation where a client type of default vs
default_failover will result in a hang with default and recommending
default_failover instead. That said, I can understand how that could be the
case so I have modified FlumeAvroManager to always use default_failover in
revision 1601541. Please verify and close.
> 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
> Fix For: 2.0-rc2
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
