camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4876) Add support for a "back-off multiplier" capability to the ScheduledPollConsumer
Date Tue, 12 Feb 2013 16:09:12 GMT


Claus Ibsen commented on CAMEL-4876:

I am not too fond of the changing re-scheduling the task.

Wonder if we can just skip polls instead. So if you have been idle for X last polls. Then
only poll every Y instead. Then we can keep the scheduler as is.

So if you have. Have to come up with good option names

Which means that if we have been idle for the last 3 polls (eg the idleThreshold option).
Then only poll every 5th time instead. And as we have a delay of 1 second, that means we will
now only do a poll every 5 x 1s = 5s.

> Add support for a "back-off multiplier" capability to the ScheduledPollConsumer
> -------------------------------------------------------------------------------
>                 Key: CAMEL-4876
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Ashwin Karpe
> Usually files or tables are only updated once a day or even once a week in a batch like
fashion. When this happens its of course important to process as fast as possible (using the
default 500 ms delay), but most of the time when there is no activity, polling every 500 ms.
is not necessary and takes system resources when running many polling routes on the same box.
> I was thinking that the ScheduledPollConsumer could be more dynamic by introducing a
new option eg. backoffMultiplier, that resets the scheduler to maxDelay if a poll results
in no exchange (maybe after x polls with no results). 
> The same goes if a poll results in an exchange, and the delay currently is at backoffMultiplier
the scheduler is reset to the original delay thereby polling more agresive again. 
> Original Camel User Forum request :

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message