[SERVER-50907] Shard objects should cache their own connection strings Created: 14/Sep/20  Updated: 29/Oct/23  Resolved: 28/Sep/20

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

Type: Bug Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-51103 RSM calls updateReplSetHosts() with p... Closed
Related
related to SERVER-46202 Implement ShardRegistry on top of Rea... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-05
Participants:
Linked BF Score: 16

 Description   

Currently, calling getConnString() on a ShardRemote object reaches back into the RSM to determine the connection string. This can result in taking an RSM mutex, and so requires care around which mutexes are held when calling getConnString().

However, the reworking of the RSM-related ShardRegistry functionality on SERVER-46202 (specifically _latestConnStrings) means that this behaviour should no longer be necessary. Instead, Shard objects should now be able to simply remember and use the connection string they were created with (ie. what is currently called originalConnString(), which could then go away).



 Comments   
Comment by Githook User [ 26/Sep/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-50907 Make Shard objects cache their own connection strings
Branch: master
https://github.com/mongodb/mongo/commit/73232929e23127b555cd315eace05c80971f8a5e

Generated at Thu Feb 08 05:23:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.