[
https://issues.apache.org/jira/browse/FLUME-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149853#comment-13149853
]
E. Sammer commented on FLUME-827:
---------------------------------
Will:
The idea is that the group is expanded. It's a logical construct, not physical.
In other words, it's config syntax sugar only. The user says clients (sinks) a,
b, and c are in group 1 and servers (sources) x and y are also in group 1. Now,
flume understands it can load balance sinks a, b, and c to sources x and y.
This is the same idea as Flume OG's autoChain (except we'd load balance rather
than stick to a single server although I suppose that could be another policy
option). At least this was my thinking / idea.
> 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
