tests: handle ambiguous collection retries in cluster#392
Merged
apetenchea merged 1 commit intomainfrom Apr 6, 2026
Merged
Conversation
…uster In cluster runs, creating an autoincrement collection can fail with 503 while the collection creation has already gone through during a coordinator or shard leadership change. The test then retries with the same collection name, gets 409 responses, and eventually reports a false failure. This is not an autoincrement bug itself. The problem is that the test treats every CollectionCreateError as a hard create failure and never checks whether the collection became visible after the error.
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
1 participant
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.
In cluster runs, creating an autoincrement collection can fail with 503 while the collection creation has already gone through during a coordinator or shard leadership change.
The test then retries with the same collection name, gets 409 responses, and eventually reports a false failure.
This is not an autoincrement bug itself. The problem is that the test treats every
CollectionCreateErroras a hard create failure and never checks whether the collection became visible after the error.