[
https://issues.apache.org/jira/browse/FLUME-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140952#comment-13140952
]
E. Sammer commented on FLUME-827:
---------------------------------
Will:
I was thinking about this and was thinking that the client should retry
indefinitely (with warnings in the logs). The rationale is similar to that of
FLUME-823. In this case, though, there's the potentially common possibility
that the Avro server to which the client is connecting (e.g. another flume node
in a tiered collection deployment) disappears temporarily (e.g. is restarted, a
network partition). Ideally, the client would reestablish the connection, in
this case, and continue transferring data. Thoughts?
> Avro client conn failure results in 60-second wait before terminating
> ---------------------------------------------------------------------
>
> Key: FLUME-827
> URL: https://issues.apache.org/jira/browse/FLUME-827
> Project: Flume
> Issue Type: Bug
> Components: Node
> Affects Versions: NG alpha 1
> Reporter: Will McQueen
> Fix For: NG alpha 2
>
>
> Launching the avro client when the Flume NG node isn't yet running will
> result in a conn refused error. The client should then shutdown immediately,
> but instead waits for 1 minute before the client is terminated.
--
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
