[SERVER-15402] Improve ShardPtr/ConnectionString management for commands and setVersion Created: 25/Sep/14  Updated: 19/Oct/15  Resolved: 19/Oct/15

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

Type: Improvement Priority: Minor - P4
Reporter: Greg Studer Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Participants:

 Description   

After some profiling of mongos performance, seems like we have some low-hanging fruit with broad impact around creating too many copies of Shards during versioning operations and (potentially related) building copies of ConnectionStrings from Shard hostnames.



 Comments   
Comment by Andy Schwerin [ 19/Oct/15 ]

The mongos refactor during 3.1 development should have taken care of this, and certainly invalidated any profiling analysis done on earlier versions.

Comment by Githook User [ 15/Oct/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-15402 Improve ShardPtr/ConnectionString management for commands and setVersion

Make Shard almost logically immutable. The only non-const method remaining is reset(), which will eventually be removed.
Branch: master
https://github.com/mongodb/mongo/commit/126069374744c62c65fac86a492531d658961f40

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