[SERVER-13126] Honor read preference after replica fail-over in 2.4 Created: 10/Mar/14  Updated: 06/Dec/22  Resolved: 23/Oct/18

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

Type: Bug Priority: Major - P3
Reporter: Andre Spiegel Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

If you read from a secondary through a mongos, and the underlying replica set has a fail-over, such that the secondary becomes a primary, mongos will still keep reading from that node, even though it is now in violation of the read preference. (Connections are pinned.)

This behavior is fixed in 2.6, but not in the 2.4.x branch. It is suggested to backport the fix, or create a different fix in 2.4 such that read preferences are honored even in the face of replica fail-overs.



 Comments   
Comment by Gregory McKeon (Inactive) [ 23/Oct/18 ]

This is 2.4 specific, which is no longer supported.

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