Description

In these pages:

https://docs.mongodb.com/manual/reference/read-preference/

https://docs.mongodb.com/manual/core/read-preference-mechanics/#read-preference-for-sharded-clusters

There is no explanation/warning that reading from a secondary can potentially opt the request out from shard versioning protocol with the default read concern of available. It is somewhat hinted in the read concern page:

https://docs.mongodb.com/manual/reference/read-concern-available/

Perhaps this should be mentioned in the read preference page (at least in the sharded version)

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)