-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The naming of the new retryAfterMS field in 9.0 does not accurately reflect the behavior it creates in the driver. The driver treats the value of the field as the base backoff for exponential retry logic, overriding the driver's base backoff. Using the name baseBackoffMS is more representative of this behavior.