Implement retry strategy #167
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #166
Exposes a
RetryStrategythat can be configured at theBusConfigurationlevel on startup.This allows the consumer to choose or provide a new strategy that determines the delay between retry attempts on message failures. By default, a
DefaultRetryStrategyis provided that delays a message between 5ms to 2.5hrs with a jitter of 10% per retry to avoid any deadlock retries.All transports except RabbitMQ have implemented this. Rabbit cannot cleanly leverage a retry strategy as messages are immutable, and the way retries are achieved is to redrive failures to a retry queue that has a static TTL.