Because the ReplicaSetMonitor (and therefore the Targeter) and the ShardRegistry are decoupled, you may try to target a recently detected CSRS node before it's been added into the config shard in the ShardRegistry, which will cause the ShardingNetworkConnectionHook to fail to establish a connection to it with a ShardNotFound error
- is related to
-
SERVER-20294 Race condition in shard targeting logic results in "Shard not found" error
-
- Closed
-
-
SERVER-19608 Send shard initialization data when talking through NetworkInterface
-
- Closed
-