[DOCS-7102] on 'primaryPreferred, clarify the situations when secondary read may occur Created: 05/Feb/16 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Annette Morrissey (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | groom | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
https://docs.mongodb.org/manual/reference/read-preference/#primaryPreferred "In most situations, operations read from the primary member of the set. However, if the primary is unavailable, as is the case during failover situations, operations read from secondary members." Could we clarify what other scenarios can make the primary "unavailable" e.g. when the primary is under heavy load, or provide a list of possible scenarios where the read could be diverted to secondaries. |
| Comments |
| Comment by Education Bot [ 01/Nov/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! |