-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.1
-
Component/s: Sharding
-
None
-
ALL
Whenever a new ShardConnection is created, checkShardVersion is called on every single shard. If you have many shards, and/or multiple shards are in mid-failover at that time, your mongos can wind up spending a ton of time making failing setShardVersion calls, rendering the mongos useless until it is restarted.
- duplicates
-
SERVER-5625 New sharded connections to a namespace trigger setShardVersion on all shards
- Closed