[SERVER-11956] using RCAR option un-pins secondaries from client connections Created: 04/Dec/13  Updated: 10/Dec/14  Resolved: 28/Feb/14

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Daniel Pasette (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

ReleaseConnectionsAfterResponse changes the way in which queries are pinned to secondaries - under load slaveOk queries to secondaries should still have even distribution, but the previous behavior of talking to the same secondary if the same connection was used (except on secondary failure) is no longer enforced.

In 2.6 RCAR is hardcoded to "on" - we re-use connections between requests.



 Comments   
Comment by Scott Hernandez (Inactive) [ 04/Dec/13 ]

Do we have anything to address the possibility that we may switch back/around in time wrt/replication, yet? Or are we just documenting that as expected "eventual consistency" behavior if reading from secondaries?

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