Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Prod
*Location*: http://docs.mongodb.org/manual/core/read-preference/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: core/read-preference
Prod *Location*: http://docs.mongodb.org/manual/core/read-preference/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: core/read-preference
Description
In most situations, operations read from secondary members but if no secondary members are available, operations read from the primary.
Should this read "operations read from secondary members but if no secondary members are available, operations read from the primary."
I am not sure I understand "In most situations"
We also aren't seeing this actually work in our code. We have implemented tagging for dataCenters and using secondaryPreffered. We have not seen a drop in queries to the primary.
Thanks