[DOCS-13217] Clarify role of *voting* nodes in majority read concern Created: 12/Nov/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: | David Bartley | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
DescriptionThe docs around majority write concern are relatively clear that only voting nodes are counted, but docs on majority read concern do not mention anything about whether non-voting nodes (and, I suppose, non-data-bearining nodes) can . Off the top of my head, the following should be clarified:
Compare this to wording in e.g. https://docs.mongodb.com/manual/reference/write-concern/: "Requests acknowledgment that write operations have propagated to the majority (M) of data-bearing voting members." Scope of changesImpact to Other DocsMVP (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! |