-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding NYC
-
Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10
-
26
-
2
It looks like StreamableReplicaSetMonitor::getHostsOrRefresh doesn't actually wait for refresh to update the latest topology before trying to get hosts after requesting an async refresh
It's not clear whether this was intentional or maybe I misread the code.
The purpose of this ticket is to investigate if we want to keep this async or not by looking at the usages of StreamableReplicaSetMonitor::getHostsOrRefresh.