-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(NODE-4863): do not use RetryableWriteError for non-server errors #3914
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
fix(NODE-4863): do not use RetryableWriteError for non-server errors #3914
Conversation
…e-write-label-for-non-server-errors
…e-write-label-for-non-server-errors
durran
left a comment
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.
Just notes for other reviewers, the testing requirements made it seem to me like the prose test #2 should change somehow, but checking the spec this test matches so no change actually needed there.
The second testing requirement I'm not sure where that came from but I think the additional unit test added here suffices.
…3914) Co-authored-by: Durran Jordan <[email protected]>
Description
Use the
MongoErrorLabel.PoolRequstedRetrylabel instead of misusedMongoErrorLabel.RetryableWriteErrorfor non-server errors according to spec.What is changing?
PoolClearedErrorconstructor adds the newMongoErrorLabel.PoolRequstedRetrylabel instead of misusedMongoErrorLabel.RetryableWriteError.isRetryableWriteErrorfunction checks if PoolRequstedRetry or RetryableWriteError is set to determine ifretryOperationis required.Is there new documentation needed for these changes?
None
What is the motivation for this change?
NODE-4863
Double check the following
npm run check:lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript