Add retries to publishing events #39
Merged
Conversation
This file contains hidden or 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
Contributor
|
👍 |
Sending of messages is moved to a background thread, so that waiting between retries does not block the user waiting for http response. The database transaction still succeeds even if message publishing fails after all retries. Failed messages are logged for monitoring. JIRA: RHELCMP-14891 Assisted-By: Claude
lubomir
force-pushed
the
more-resilient-umb
branch
from
2885d4d to
a6a3718
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sending of messages is moved to a background thread, so that waiting between retries does not block the user waiting for http response.
The database transaction still succeeds even if message publishing fails after all retries. Failed messages are logged for monitoring.