Details
-
Improvement
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
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