Handle ReadTimeout from actinia with retries#65
Merged
ninsbl merged 6 commits intoactinia-org:mainfrom Mar 5, 2026
Merged
Conversation
anikaweinmann
approved these changes
Mar 5, 2026
Member
anikaweinmann
left a comment
anikaweinmann
left a comment
There was a problem hiding this comment.
Thank you very much. The change looks good and very helpful.
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
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.
We occasionally experience ReadTimeout from
actiniaunder high ressource usage.The asynchounous processing continues fine, but it takes too long to get a status response and the client throws an exception, leading us to restart a job that is already running. That is esp. unfortunate as it further increases the system load that is already high and may lead race conditions and other failures...
Instead of failing right away, it would be great to allow for retries in that case. For now, we do catch those cases in our local code, but it would of course be more meaningful to have it in the client....
This PR implements retries in case of ReadTimeout.
Happy to adjust the code as prefered...