You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/11/01 01:29:17 UTC

[jira] [Commented] (FLUME-2229) Backoff period gets reset too often in OrderSelector

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

Jarek Jarcec Cecho commented on FLUME-2229:
-------------------------------------------

The Jenkins failure do not seem to be relevant - the job is failing for some time already.

> Backoff period gets reset too often in OrderSelector
> ----------------------------------------------------
>
>                 Key: FLUME-2229
>                 URL: https://issues.apache.org/jira/browse/FLUME-2229
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>         Attachments: FLUME-2229.patch
>
>
> In OrderSelector.java, the backoff period is calculated by using the number of sequential failures seen to the same host. Since CONSIDER_SEQUENTIAL_RANGE is set to 2 seconds, if the host is not selected for connection within 2 seconds of the backoff period ending, the sequential failures variable is reset and backoff period is not increased. 
> We must increase the value of CONSIDER_SEQUENTIAL_RANGE so that the backoff is not reset too often.



--
This message was sent by Atlassian JIRA
(v6.1#6144)