-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In SERVER-123628, we set a limit for 10 retries for the authoritative refresh path. However, this turned out to be insufficient (SERVER-125690) so we increased the number of retries to 100 in SERVER-125973.
We should understand why the initial limit of 10 retries was insufficient, and based on this determine the best retry limit (high enough to prevent spurious failures, but low enough to catch inefficiencies/regressions).
- is related to
-
SERVER-125690 timeseries_create_indexes.js in concurrency_sharded_replication_with_balancer
-
- Closed
-
-
-
- Closed
-
-
SERVER-123628 Limit retry attempts in _recoverCollectionMetadataFromDisk recovery loop
-
- Closed
-