Ignore the 404 error when deleting the bucket to make it more resilie… #161
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.
…nt to transient errors.
Bug Description
We encounter an unhandled exception which is caused by an error code 404 when calling
DeleteBucketAsync
to delete an existing S3 bucket. The exception is unexpected because the existing bucket should be successfully deleted and no 404 exception should be thrown.We found that the retry mechanism of
DeleteBucketAsync
can actually lead to a 404 error even if the bucket exists when issuing the deletion. More concretely:DeleteBucketAsync
sends a HTTP request to delete the bucketExpected behavior & Possible Solution
As implemented in this PR:
I hope this can help! Thanks.