[DOCS-12797] Improve documentation around doing secondary reads in sharded clusters Created: 12/Jun/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-41258 Router config remains stale for secon... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

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.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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