-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding
-
v4.0
This fixes a regression introduced in 4.0.
However, a user should be running flushRouterConfig against all routers and shards after a dropDatabase or movePrimary, which would prevent this and other issues from occurring.
- is related to
-
SERVER-32871 ReplicaSetMonitorRemoved and ShardNotFound errors on fanout query after removing a shard
- Closed