-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-09-30, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-11-11
-
(copied to CRM)
-
200
Our current backoff strategy for write conflicts is very rudimentary and susceptible to several problems:
- It retries too many times without any backoff. We should consider only doing this once or twice before starting to sleep
- It doesn't ramp up the expontential backoff fast enough. We would need to reach 310 retry attempts before backing off to 100ms, which is likely way too impactful.
- It does not have jitter, which would randomizes retry attempts by concurrent operations
- The maximum sleep of 100ms could still be too fast for some workloads
- is related to
-
SERVER-65418 Query plan executor must release resources before backing off
-
- Backlog
-
-
SERVER-96726 Lower the artificial conflict rate in collMod_writeconflict.js tests
-
- Closed
-
- split to
-
-
- Needs Scheduling
-