[
https://issues.apache.org/jira/browse/FLUME-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Mujumdar updated FLUME-927:
----------------------------------
Attachment: Flume-927.patch.1
> A Flume agent started before collectors in E2E mode could fail to connect to
> the collector
> ------------------------------------------------------------------------------------------
>
> Key: FLUME-927
> URL: https://issues.apache.org/jira/browse/FLUME-927
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v0.9.4, v0.9.5
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: v0.9.5
>
> Attachments: Flume-927.patch.1
>
>
> The write ahead log (WAL) mechanism expects the agent sink to be active in 1
> second. After that, it assumes that the agent couldn't connect to collector
> and shuts it down. The AgentSink has a retry mechanism that handles network
> problems, unavailable collector etc for a configurable amount of time. The
> hardcode 1 sec timeout in WAL decorator invalidates this retry mechanism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
