Matt, I don't know if this helps, but we are seeing similar issues with Flume using log4j2 (not log4j v1 as used by ES). For tomcat-hosted servlets, flume failover works fine. But for non-tomcat applications (such as looping batch-mode applications and Netty-based servers with static main entry points), we have found that when one of their flume loggers fails, there is no failover.
We don't have a solution. But a workaround is that the non-tomcat applications only configure their log4j to write to one flume agent. If that fails, events are queued until the agent comes back up. No failover, but no data loss either. Brian -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e51a0926-7742-4cd7-877d-1c1d12ed2a1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
