-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Networking, Replication
-
None
-
Fully Compatible
-
Service Arch 2018-12-31
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
There's a TODO here with no corresponding ticket.
The getHostOrRefresh function is used in shard targeting, including from a function "findHostNoWait". The expectation for that function is that no waiting happens, even on error. Instead, we spawn an extra thread anyways even though we know we won't retry.
- is duplicated by
-
SERVER-21431 Sharding host targeting logic should use the remaining time from the OperationContext as a timeout
-
- Closed
-