Support redis max_receives
config option
#100
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a
max_receives
option to both Redis queue implementations.This is the first step in supporting deadletter queuing.
InternalPayload
type aliases have been added to represent Omniqueueitems that track the current number of times a message has been
received (
num_receives
).num_receives
is incremented wheneveran item is re-queued from the pending/processing queues until it
hits
max_receives
, at which point the message is abandoned. Laterwe will support putting this in an optional deadletter queue.
I originally tried adding a proper struct for
InternalPayload
, butI don't think that clarified anything and was less memory optimal,
so the relevant logic has been captured in simple functions/macro
instead.