[DOCS-872] Incorrect specification of how nodes are chosen for "nearest" read preference Created: 11/Dec/12  Updated: 17/Jan/13  Resolved: 16/Jan/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: sam.helman@10gen.com Assignee: Ed Costello
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 11 years, 5 weeks ago

 Description   

On the page http://docs.mongodb.org/manual/applications/replication/#nearest, it states that

"If you specify a tag set, the client attempts to find a secondary member that matches the specified tag set and directs reads to a random secondary from among the nearest group."

This makes it seem that the "nearest" read preference in combination with tag sets only allows reading from secondaries, which is incorrect.

Additionally, the use of the word "random" is misleading because the choice of node depends on implementation. Recommended is either removing it or replacing with "arbitrary".



 Comments   
Comment by auto [ 16/Jan/13 ]

Author:

{u'date': u'2013-01-16T17:23:54Z', u'email': u'epc@10gen.com', u'name': u'Ed Costello'}

Message: DOCS-872 rewrite comments about nearest and tag sets and member selection
Branch: master
https://github.com/mongodb/docs/commit/863ebbd9b22f1c8278622cef8acf9d21e885390f

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