when adding or removing a member from a replica set via a reconfig, mongos does not always update the config.shards collection. Seems to update on startup, but not on general reconfig.
Test case reproduces.
- is duplicated by
-
SERVER-4453 Shards not picking up replica set updates
- Closed
- related to
-
SERVER-7278 mongos doesn't always update shards in response to replica set changes
- Closed