-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The design document specifies that we must use a shared pointer of the RetryBudget of a AdaptiveRetryStrategy. However, we may have a path for defining a clear lifetime relationship. A Shard::RetryStrategy cannot live longer than the Shard it was created for. This is an opportunity to change it to a value and use non owning pointers instead of shared pointers.
However, we must evaluate if this is possible to do after doing implementation work for the asynchronous code paths.
- duplicates
-
SERVER-110662 Keep the shard retry budget per shard id instead of per Shard instance
-
- In Progress
-
- related to
-
SERVER-111888 Complete TODO listed in SERVER-109573
-
- Open
-
-
SERVER-110662 Keep the shard retry budget per shard id instead of per Shard instance
-
- In Progress
-