[SERVER-14899] Re-evaluate the behavior of connection pinning in mongos Created: 14/Aug/14  Updated: 26/Apr/19  Resolved: 13/Jul/15

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

Type: Question Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-9788 mongos does not re-evaluate read pref... Closed
related to SERVER-13542 Expose electionId on primary in isMaster Closed
Participants:

 Comments   
Comment by Ian Whalen (Inactive) [ 26/Apr/19 ]

Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed.

Comment by Andy Schwerin [ 13/Jul/15 ]

We are moving away from connection pinning, as are the drivers.

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