-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Additional errors are now considered for retryable writes, resumable change stream operations, and "not master"/"node is recovering" errors in SDAM. See spec changes below :
- https://github.com/mongodb/specifications/commit/7021f759c4c2a918808660a2e4e55ba1f4e4acb5
- https://github.com/mongodb/specifications/pull/307
Following changes have been done to the retryable writes tests :
- Changed the format of the "failPoint" field, see https://github.com/mongodb/specifications/commit/035c987b0b99a22b49703c64f91195010fa1f6b4#diff-c74e7320652f60d5defb81f16066278eL143
- Added retryableErrors.yml to test all the retryable error codes added in SPEC-1051 using the failCommand failpoint added in MongoDB 3.7.
- depends on
-
CDRIVER-2638 Retryable writes should consider more errors retryable
- Closed
-
GODRIVER-402 Retryable writes should consider more errors retryable
- Closed
-
MOTOR-218 Retryable writes should consider more errors retryable
- Closed
-
NODE-1456 Retryable writes should consider more errors retryable
- Closed
-
PHPC-1181 Retryable writes should consider more errors retryable
- Closed
-
PYTHON-1545 Retryable writes should consider more errors retryable
- Closed
-
RUBY-1333 More errors should be retryable
- Closed
-
RUST-77 More errors must should be considered retryable
- Closed
-
CSHARP-2229 Retryable writes should consider more errors retryable
- Closed
-
CXX-1572 Retryable writes should consider more errors retryable
- Closed
-
JAVA-2847 Retryable operations should consider more errors retryable
- Closed
- is duplicated by
-
DRIVERS-482 Should certain writeConcernErrors be "not master" errors
- Closed
-
DRIVERS-483 Resync retryable writes test
- Closed
-
DRIVERS-495 Test every "not master" error code in retryable writes test
- Closed