-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
SERVER-88000 made writeConflictRetry use an exponential backoff and concluded that the existing truncated linear backoff was appropriate for read conflicts in plan execution. Write conflicts in UpdateStage don't fall into either of those, and may also benefit from a better conflict backoff strategy.
- split from
-
SERVER-88000 Implement real exponential backoff and jitter in write conflict retry
- Closed