resource/aws_dynamodb_table: Allow simultaneous region deletion retry of 5 minutes to better handle global table deletions #5518
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.
When DynamoDB is deleting multiple regions of a global table, the deletion call can get stuck waiting for another deletion call to finish. This can be seen with the very consistently failing acceptance test:
Changes proposed in this pull request:
aws_dynamodb_table
resource deletion function to allow DynamoDB to get around to deleting other regions simultaneously. Increasing the threshold to 2 minutes still was flakey with our empty DynamoDB global table, so decided on 5 minutes as the retry threshold since the retry conditions are fairly safe. In some regards this is a guess that it shouldn't instead bed.Timeout(schema.TimeoutDelete)
, which is already used with the wait for deletionStateChangeConf
.Output from acceptance testing: