-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Fully Compatible
-
ALL
-
Sharding 12 (04/01/16), Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16)
-
0
When we create a ReplicaSetMonitor for a replica set for the first time we don't kick off a refresh of that replica set. The ReplicaSetMonitorManager will eventually refresh it, but it only refreshes all sets once every 10 seconds. This means there can be a period of 10 seconds or more (if it has to wait for other sets to be refreshed first) before all nodes of a replica set are discovered. This can cause us to neglect certain secondaries for secondary reads, preventing us from evenly distributing the read load of secondary reads until after the full refresh takes place.
- is duplicated by
-
SERVER-23890 Refresh ReplicaSetMonitor using TaskExecutor, get rid of ReplicaSetMonitorWatcher
- Closed
- related to
-
SERVER-22494 shard6.js test needs to account for ReplicaSetMonitor
- Closed