[SERVER-4498] Creating a ShardConnection calls checkShardVersion on every shard Created: 15/Dec/11  Updated: 19/Nov/12  Resolved: 19/Nov/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5625 New sharded connections to a namespac... Closed
Operating System: ALL
Participants:

 Description   

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.


Generated at Thu Feb 08 03:06:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.