[DOCS-2717] Read Preferences entry improvements Created: 13/Feb/14  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 47 weeks, 2 days ago

 Description   

Under "use cases," replace the "maximize throughput" paragraph that Asya removed. The replacement graf should not mention maximizing throughput or that it's a remedy for disk-IO-bound workloads; instead, it should say that "nearest" with high secondaryAcceptableLatencyMS is for "evenly distributing query load across all members" for read-only analytics apps.

While we're at it, introduce a section like this one that describes the server selection algo:

http://emptysqua.re/blog/reading-from-mongodb-replica-sets-with-pymongo/#algorithm



 Comments   
Comment by Sam Kleinman (Inactive) [ 24/Mar/14 ]

I think the following section addresses your interest in describing the server selection algo: http://docs.mongodb.org/manual/core/read-preference-mechanics/#member-selection

The problem here, I think is in linking this to this http://docs.mongodb.org/manual/core/read-preference/ page more clearly and usefully.

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