API engine retry #63
Merged
API engine retry #63
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
Adds a engine API retry which will continue to retry an API call if the API currently reports that the API is closed. This is useful for when leadership changes are in progress (typical during boot where leaders are actively being shuffled). The retry will continue to retry an active API call every 300ms when the API reports as closed (because leadership has caused the API to be closed). The retry will continue to cancel calls if the caller has cancelled the context, or if the cron is shutting down. Signed-off-by: joshvanl <me@joshvanl.dev>
yaron2
approved these changes
Jan 14, 2025
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.
Adds a engine API retry which will continue to retry an API call if the API currently reports that the API is closed. This is useful for when leadership changes are in progress (typical during boot where leaders are actively being shuffled). The retry will continue to retry an active API call every 300ms when the API reports as closed (because leadership has caused the API to be closed). The retry will continue to cancel calls if the caller has cancelled the context, or if the cron is shutting down.