-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
To aid in troubleshooting exceptions surfaced from the driver to the application, we would like all such exceptions that are a result of an operation to contain the following additional information:
- The server to which the operation was sent
- Whether the first attempt failed or a retry
While implementing this change, the following additional retry logic-related aspects were also added to the additional diagnostics:
- If retryable reads/writes are enabled but the retry is not performed, such as due to the new server not supporting retries, this is stated
- If the retry is performed but original exception is raised, this is stated
- depends on
-
RUBY-1904 Consolidate response handling code in operations layer
- Closed
- is related to
-
RUBY-1954 Integration test for exceptions referencing second attempt's server for retryable operations
- Closed
-
DRIVERS-2170 Errors on retryable ops should indicate originating server when possible
- Implementing
- links to