storage: re-add retries for s3 delete_prefix#3364
Merged
Merged
Conversation
github-actions
Bot
added
the
S-waiting-on-review
GuillaumeGomez
approved these changes
Jun 12, 2026
Member
|
Looks good to me, thanks! |
github-actions
Bot
added
S-waiting-on-deploy
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.
Digging into an error with the
repackagecommand, I realized theDeleteObjectsAPI only retries for errors in the main api call, and doesn't retry single failed objects on mixed responses (where some deletes fail, and some succeed).See https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html#API_DeleteObjects_Examples
Here we add it back.
On top, I'm adding parallelization if we have to delete more than 1000 objects.