-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
More errors should be retryable. See spec changes below :
Add retryable error codes & code names to write retry logic
Expand write retry cases
Review server source for additional write retry messages not in current spec
Expand change stream resume cases
Write change stream resume tests
Make change streams retry on getMore only
Review read retry code
Test cases:
Retry on a non-write concern error
Fail on a non-write concern error
Retry on a write concern error
Fail on a write concern error
Retry on change stream initiation
Fail on change stream initiation
Retry on change stream getMore
Fail on change stream getMore
- depends on
-
RUBY-1331 Errors raised by drivers should include codeName string from server response
- Closed
- is depended on by
-
DRIVERS-467 More errors must should be considered retryable
- Closed
- is duplicated by
-
RUBY-1327 Initial aggregate command for a change stream should not be retried
- Closed