[SERVER-7606] Refactor how shard version information is associated with each connection Created: 09/Nov/12  Updated: 07/Mar/14  Resolved: 07/Mar/14

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-7460 Issue with threads re-using previousl... Closed
related to SERVER-1714 multiplex mongos -> mongod connecions... Closed
Participants:

 Description   

Currently there's a map in s/shard_version.cpp that associated each client connection with a shard version. Might be better to store that version in each thread's thread-local ClientBase object.



 Comments   
Comment by Greg Studer [ 07/Mar/14 ]

We're moving away from this version cache in general.

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