-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Retryability
-
Needed
Summary
DRIVERS-746 introduced spec language around retrying handshake errors, and there is still some ongoing discussion regarding whether that specification is complete. Regardless of the specific criteria for retryable errors, it is clear that not all handshake errors should be retryable (depending on the error type as well as the retryable reads/writes client settings); however, there are currently no spec tests for asserting that a driver should not retry particular handshake errors given some set of conditions. This could result in driver implementations that incorrectly retry on every handshake error regardless of error type, code, or client retryability settings.
Is this ticket only for tests?
Yes
- is related to
-
NODE-4206 Add coverage for non retryable error codes
- Blocked
- related to
-
DRIVERS-1842 Drivers should retry authentication errors when connection handshake fails
- Backlog
-
DRIVERS-746 Drivers should retry operations if connection handshake fails
- Implementing
- split to
-
CDRIVER-4322 Add tests for non-retryable handshake errors
- Blocked
-
CSHARP-4123 Add tests for non-retryable handshake errors
- Blocked
-
CXX-2479 Add tests for non-retryable handshake errors
- Blocked
-
GODRIVER-2363 Add tests for non-retryable handshake errors
- Blocked
-
JAVA-4557 Add tests for non-retryable handshake errors
- Blocked
-
NODE-4150 Add tests for non-retryable handshake errors
- Blocked
-
PHPLIB-830 Add tests for non-retryable handshake errors
- Blocked
-
PYTHON-3195 Add tests for non-retryable handshake errors
- Blocked
-
RUBY-2941 Add tests for non-retryable handshake errors
- Blocked
-
RUST-1249 Add tests for non-retryable handshake errors
- Blocked
-
MOTOR-921 Add tests for non-retryable handshake errors
- Closed