Loading...

XML

Word

Printable

JSON

Upstream Changes Summary:
Hide

DRIVERS-3446:
Summary of necessary driver changes

Drivers must ensure their retry logic correctly follows the spec by setting the maximum number of retries for ALL retryable errors, regardless of policy, to MAX_RETRIES when an overload error is encountered.

Full clarification in 7039e69945d463a14b1b727d16db063e21f48f53.

Commits for syncing spec/prose tests
(and/or refer to an existing language POC if needed)

Four new prose tests in 7039e69945d463a14b1b727d16db063e21f48f53.

Context for other referenced/linked tickets
Show
DRIVERS-3446 : Summary of necessary driver changes Drivers must ensure their retry logic correctly follows the spec by setting the maximum number of retries for ALL retryable errors, regardless of policy, to MAX_RETRIES when an overload error is encountered. Full clarification in 7039e69945d463a14b1b727d16db063e21f48f53 . Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) Four new prose tests in 7039e69945d463a14b1b727d16db063e21f48f53 . Context for other referenced/linked tickets
Confidence Status:
None

Documentation Changes:
Not Needed
Documentation Changes Summary:

Hide

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?

Show
1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

This ticket was split from DRIVERS-3446, please see that ticket for a detailed description.

depends on

GODRIVER-3844 Finalize client backpressure implementation for phase 1 rollout

split from

DRIVERS-3446 Add prose tests to verify correct retry behavior when a mix of overload and non-overload errors are encountered