You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2014/01/11 05:06:51 UTC

[jira] [Commented] (FLUME-2296) Flume RPC back off bug

    [ https://issues.apache.org/jira/browse/FLUME-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868647#comment-13868647 ] 

Hari Shreedharan commented on FLUME-2296:
-----------------------------------------

Have you tried the trunk code? The reason this was happening was that the timeout was getting reset too often. Can you try trunk and see if you hit this issue?

> Flume RPC back off bug
> ----------------------
>
>                 Key: FLUME-2296
>                 URL: https://issues.apache.org/jira/browse/FLUME-2296
>             Project: Flume
>          Issue Type: Bug
>          Components: Client SDK
>    Affects Versions: v1.4.0
>         Environment: Java application use LoadBalancingLog4jAppender
>            Reporter: edwardsbean
>
> I'm using LoadBalancingLog4jAppender.To be failoverUnder the condition of one of log server is down. If I set a max back off time,LoadBalancingLog4jAppender will try to reconnect log server after a time( generate by exponential backoff algorithm in class OrderSelector)
> The problems is that, the time generate by exponential backoff algorithm always be 2000ms. not increating by algorithm.
> If I change the condition (allowableDiff > delta) to (allowableDiff < delta), it works fine. from line 103 of OrderSelector



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)