-
Type: Bug
-
Resolution: Done
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/core/read-preference/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: core/read-preference
*Location*: http://docs.mongodb.org/manual/core/read-preference/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: core/read-preference
This statement is NOT true:
For queries of sharded collections that do not include the shard key, secondaries may return stale results with missing or duplicated data because of incomplete or terminated migrations.
It is when you DO include the shard key that you have problem.