[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exponential backoff for Scheduler Component

Thank you my friend for taking time to look into this. Glad to hear from you, even so publicly :-)

Although I'm not complete camel novice, I'm using it after very long time. So it is quite possible that
I misunderstood or forgot some important concepts.

With that aside, let me explain my use case in some more details.

I have a scheduled polling consumer which looks into a database for records with appropriate status.
If those are not found, polling consumer stays idle and does not route exchange any further. If error
occurs, I think it is enough to backoff and try again without any meaningful error handling:

// code in groovy
    .process({ Exchange exchange ->
        String serviceBeanName = EupEventPublisherForCamelService.simpleName.uncapitalize()
        EupEventPublisherForCamelService eupEventPublisherForCamelService = exchange.context.registry.lookupByNameAndType(serviceBeanName, EupEventPublisherForCamelService)

        List<EupEventPublisherEntity> eventList = eupEventPublisherForCamelService.findAllNonPublishedEventsForCamelRoute()
        exchange.in.body = eventList

        if (eventList.size() < 1) {
          // Indicate to scheduler that there was no results, so it can backoff
          exchange.setProperty(Exchange.SCHEDULER_POLLED_MESSAGES, false)

          // Stop routing further since we do not want empty exchanges to end up in jms broker.
          exchange.setProperty(Exchange.ROUTE_STOP, true)

Maybe I can throw some exception to signal idle case, but it looks too harsh to do. In addition,
I don't really know how DLC redelivery and scheduler interplay in such scenario. I guess DLC
redelivery will not stop scheduler from firing.

I thought it would be easier to have exponential backoff in scheduler itself, so I can gradually backoff
in idle case. It would be even better to be able to configure idle and error cases independently (something
like backoffIdleMultiplier and backoffErrorMultiplier) since, in case of errors, I would like to have
a different and bigger multiplier then for idle case.

Hope this makes some sense.

Damir Murat

Attachment: signature.asc
Description: Message signed with OpenPGP