[DOCS-6268] No secondary connection pinning in 3.0 Created: 24/Sep/15  Updated: 11/Jan/17  Resolved: 15/Dec/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-3.0
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Steven Hand Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-9788 mongos does not re-evaluate read pref... Closed
Participants:
Days since reply: 7 years, 9 weeks ago

 Description   

According to SERVER-9788, driver no longer pin connection to a given mongod instance.



 Comments   
Comment by Kay Kim (Inactive) [ 15/Dec/16 ]

This was done via overhaul of DOCS-8691

Comment by Steven Hand [ 24/Sep/15 ]

See this comment on SERVER-9788. According to that, the following text should be removed from the documentation:
Reuse a connection to a specific mongod for as long as possible after establishing a connection to that instance. This connection is pinned to this mongod.

Generated at Thu Feb 08 07:51:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.