[
https://issues.apache.org/jira/browse/FLUME-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141472#comment-13141472
]
E. Sammer commented on FLUME-827:
---------------------------------
+1 to what Ralph said. There will likely be pluggable policies that dictate how
clients (sinks) pick from servers (sources) in tiered collection deployments.
Think of not just HA but also load balancing policies. My original long design
for this was that clients would never send to servers, but instead send to a
group (which could be made up of a single server) with a policy (round robin,
sticky selection (what Ralph describes), weighted, etc.).
> 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
