Details
Description
The ReplicaSetMonitor monitors membership changes of all the known replica set shards in mongos and tries to update the ShardRegistry and config.shards. The issue is that when the ShardRegistry::reload gets called, it will clear all it's entries and tries to reread the contents from config.shards. So there is a small window were the ShardRegistry 'forgets' the newly added replSet member until config.shards get updated and reload gets called again.
Attachments
Issue Links
- is depended on by
-
SERVER-22485 ShardNotFound error when looking up replica set with hosts in a different order than is stored in the ShardRegistry
-
- Closed
-
- related to
-
SERVER-25230 ShardRegistry can temporarily forget newly added repl members
-
- Closed
-