[SERVER-7461] Possible for simultaneous aggressive chunk reload on many connections to prevent all shard versioning Created: 24/Oct/12  Updated: 15/Feb/13  Resolved: 24/Oct/12

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

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

Issue Links:
Depends
Duplicate
duplicates SERVER-7460 Issue with threads re-using previousl... Closed
Operating System: ALL
Participants:

 Description   

If you bring up many connections to a mongos at once this can cause a large amount of config reloads for the same data, causing the sequenceNumber to continually increase, preventing threads from successfully reloading config data.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 24/Oct/12 ]

SERVER-7460

Comment by Spencer Brody (Inactive) [ 24/Oct/12 ]

You can tell this is the source of the problem by looking at the mongos logs and seeing multiple stale config detected messages for the same connection, with at least one message like "ChunkManager: time to load chunks for dbname.collectionname: 3ms sequenceNumber: 1126 version: 52|1" in between them, which will increase the sequence number.

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