Durable queue sophisticated retries

[Andy Chambers]

Hi Zach,

In durable-queue, there is the retry! function which provides support for
retrying tasks but as far as I can see, there's no explicit support for
retrying a task after some delay. Where would you suggest that one should
store the data required to implement retry with an increasing backoff
algorithm for example? Am I wrong in assuming the tasks themselves cannot
be modified prior to `retry!`.

Cheers,
Andy

[Zach Tellman]

The tasks cannot be modified once enqueued. You can either have some sort
of external data structure to track retry delays, or you can enqueue a new
task and mark the failed one as `complete!`. The only risk there is that
you'll temporarily have both tasks in the queue before marking the first as
complete, and your process could crash in that moment.

Post by Andy Chambers
Hi Zach,
In durable-queue, there is the retry! function which provides support for
retrying tasks but as far as I can see, there's no explicit support for
retrying a task after some delay. Where would you suggest that one should
store the data required to implement retry with an increasing backoff
algorithm for example? Am I wrong in assuming the tasks themselves cannot
be modified prior to `retry!`.
Cheers,
Andy
--
You received this message because you are subscribed to the Google Groups "Aleph" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.