[
https://issues.apache.org/jira/browse/FLUME-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810726#comment-13810726
]
Hudson commented on FLUME-2229:
-------------------------------
FAILURE: Integrated in flume-trunk #520 (See
[https://builds.apache.org/job/flume-trunk/520/])
FLUME-2229. Backoff period gets reset too often in OrderSelector (jarcec:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=a89897bec4e7d6f3342ed966c61668e8a8139af5)
* flume-ng-sdk/src/main/java/org/apache/flume/util/OrderSelector.java
> 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)
