[DOCS-7925] Need to make clear nearest calculation not done with secondaryPreferred Created: 20/May/16  Updated: 11/Jan/17  Resolved: 24/May/16

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

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

Issue Links:
Related
Participants:
Days since reply: 7 years, 38 weeks, 1 day ago

 Description   

I reviewed the v2.6.8 code for selecting the members based on the read preference.

The nearest calculation is not used when using the "secondaryPreferred" read preference. In other words, the members selected are all secondaries and primaries regardless of ping times. If a secondary cannot be selected, then the primary is selected.

The nearest calculation is done when using the "secondary" read preference. See code.

This code has changed since 2.6.8. We should be clear about which read preferences cause the nearest calculation to be done.



 Comments   
Comment by Steven Hand [ 24/May/16 ]

My mistake. Please ignore.

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