[SERVER-42125] Avoid increasing connection count to passive secondaries with matchPrimaryNode Created: 09/Jul/19  Updated: 29/Oct/23  Resolved: 25/Jul/19

Status: Closed
Project: Core Server
Component/s: Internal Code, Networking
Affects Version/s: None
Fix Version/s: 4.2.0-rc5, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Mira Carey Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-44839 Frequent schema changes in mongos ftd... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Service Arch 2019-08-12
Participants:

 Description   

the matchPrimaryNode mode for the sharding connection pool currently spools as many connections to priority 0 nodes as to electable nodes. This isn't desirable, because those nodes won't become primary (so we don't need to stock as many connections to them).

We have this information from isMaster (in the form of the "passive" and "passives" fields), so should expose it in the rsm + use it for matchPrimaryNode



 Comments   
Comment by Githook User [ 26/Jul/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-42125 Omit passive members from RSM connection strings

(cherry picked from commit e68d63e7b048ac8b5accdd7c99dba66089859753)
Branch: v4.2
https://github.com/mongodb/mongo/commit/edcd0b9a2254cbac3d843be28f373a4f0f3024b4

Comment by Githook User [ 25/Jul/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-42125 Omit passive members from RSM connection strings
Branch: master
https://github.com/mongodb/mongo/commit/e68d63e7b048ac8b5accdd7c99dba66089859753

Generated at Thu Feb 08 04:59:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.