[
https://issues.apache.org/jira/browse/FLUME-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved FLUME-839.
----------------------------------
Resolution: Won't Fix
Fix Version/s: v0.9.5
Won't fix. 0.X branch not maintained anymore
> Agent chain doesn't switch to a backup collector if the primary one get to
> ERROR state
> --------------------------------------------------------------------------------------
>
> Key: FLUME-839
> URL: https://issues.apache.org/jira/browse/FLUME-839
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.4
> Reporter: Björn Edström
> Fix For: v0.9.5
>
>
> I have a setup like this:
> agent: source | agentDFOChain("collector1:35853", "collector2:35853")
> collector1: collectorSource(35853) |
> collectorSink("hdfs://namenode.company.net:54310/flume/", "%Y_%m_%d_%H-")
> collector2: collectorSource(35853) |
> collectorSink("hdfs://namenode.company.net:54310/flume/", "%Y_%m_%d_%H-")
> If both collectors are running, and then collector1 gets into an ERROR state
> (such as because of the FLUME-798), events are silently dropped. No fail-over
> takes place to the other node in the chain, and no events are written to disk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
