[SERVER-10901] Using read preference causes stale version info Created: 25/Sep/13  Updated: 25/Sep/13  Resolved: 25/Sep/13

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

Type: Bug Priority: Major - P3
Reporter: Charlie Page Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-10904 Possible for _master and _slaveConn t... Closed
Operating System: ALL
Participants:

 Description   

For a sharded setup there are stale config version issues when read preference primary is used.
This problem appears to go away when read preference is removed. The logs when this problem happens indicate that when a stale config is detected mongos is using a different connection when calling setShardVersion and then doing the query.



 Comments   
Comment by Charlie Page [ 25/Sep/13 ]

Duplicate of SERVER-10904

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