-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Execution Team 2024-09-30
-
(copied to CRM)
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