[CORL-1238] Duplicate User Race #3068
Merged
Conversation
This file contains 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
tessalt
approved these changes
Aug 4, 2020
wyattjoh
added
the
🚀 merge it!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
As reported in #3061, sometimes SSO authentications can cause a duplicate user error to be thrown when multiple requests are sent at the same time. This introduces a single retry if the operation fails due to a duplicate user error.
What changes to the GraphQL/Database Schema does this PR introduce?
None.
How do I test this PR?
This is pretty difficult to test in action because it involves a database race to occur. This change was motivated from the documentation provided in #3061 (comment) (seen here: https://docs.mongodb.com/manual/reference/method/db.collection.findAndModify/#upsert-and-unique-index)