[
https://issues.apache.org/jira/browse/FLUME-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810630#comment-13810630
]
Jarek Jarcec Cecho commented on FLUME-2229:
-------------------------------------------
Committed to
[trunk|https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=a89897bec4e7d6f3342ed966c61668e8a8139af5]
and
[cherry-picked|https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=7fc23d7d41757ce75058cead963b5bd54c395727]
to flume-1.5. Thank you for your contribution [~hshreedharan]!
> 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)
