-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.4.0-rc0, 4.3.5, 4.3.6, 4.4.0-rc10
-
Component/s: Sharding
-
ALL
-
35
On the reception of a isMaster response the RSM installs the new server description and possibly changes the topology type for the corespondent replica set. The same isMaster response will also trigger a NetworkConnectionHook::vlidateHost() that will try to do a reverse lookup host->shard that will fail triggering a ShardNotFound error.
- is related to
-
SERVER-48201 ShardRegistry::reload() competes with updates to the ShardRegistry through the RSM
- Closed