incubator-flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will McQueen (Commented) (JIRA)" <>
Subject [jira] [Commented] (FLUME-827) Avro client conn failure results in 60-second wait before terminating
Date Tue, 01 Nov 2011 21:49:32 GMT


Will McQueen commented on FLUME-827:

Okay, so it sounds like the client's retry policy should be configurable -- left to the client,
as Ralph says. Since each agent can act as both a client and server (sink and source, respectively),
then each sink and each source can have its own pluggable retry policy, as Eric suggests.
The behavior of FLUME-823 can also be dictated by these policies. Policies can be grabbed
from a local config file (eg,, although for a large number of agents I can
see value in some kind of central management of policies with a policy server that agents
would grab their configs from.

Eric, for the original long design where clients send events to a group node that contains
the retry policy (among other policies), if I understand correctly we'd have something like

Client ==> Group ==> Server

What would be the client's retry policy if it's now the group node disappears temporarily?
> Avro client conn failure results in 60-second wait before terminating
> ---------------------------------------------------------------------
>                 Key: FLUME-827
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message