-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRIVERS-1571 Retry on different mongos when possible #1450
DRIVERS-1571 Retry on different mongos when possible #1450
Conversation
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
Co-authored-by: Preston Vasquez <[email protected]>
|
||
2. Create a client per mongos using the direct connection, and configure fail | ||
points on each of the picked mongoses, so that each mongos raises | ||
a retryable error once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include that the failpoint should be configured with a "RetryableWriteError" label?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Added errorLabels: ['RetryableWriteError']
to the failpoint specification above.
mongoses in the cluster, pick one to test against. | ||
|
||
2. Create a client that connects to the mongos using the direct connection, | ||
and configure a fail point so that the mongos raises a retryable error once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include that the failpoint should be configured with a "RetryableWriteError" label?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Co-authored-by: Preston Vasquez <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor cosmetic tweaks. Great work! LGTM
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Co-authored-by: Alex Bevilacqua <[email protected]>
Please complete the following before merging:
Ruby PoC - mongodb/mongo-ruby-driver#2717
Go PoC - mongodb/mongo-go-driver#1358