[DOCS-11713] write/read concern read your own writes documentation is misleading Created: 16/May/18 Updated: 13/Nov/23 Resolved: 13/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-3.6, 4.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 1 |
| Labels: | reopened, triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 47 weeks, 2 days ago |
| Description |
|
https://docs.mongodb.com/master/reference/read-concern-majority/#read-your-own-writes https://docs.mongodb.com/master/reference/write-concern/#writeconcern._dq_majority_dq_ These two pages say that if you do a majority read after a majority write, you're guaranteed to read that write. If you are talking to the exact same node that is true, but drivers often don't talk to the same node. This is also an implementation detail and causal consistency is really what users should be using for this. |
| Comments |
| Comment by Ashley Brown [ 13/Mar/23 ] |
|
Hi, we're closing this ticket because we believe this problem has been fixed. If you believe this is an error, please reopen the ticket with a comment explaining why and we'll take a look. Thanks! |
| Comment by Sarah Olson [ 02/Nov/22 ] |
|
Thanks very much milkie@mongodb.com. |
| Comment by Eric Milkie [ 31/Oct/22 ] |
|
This is still relevant. |
| 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! |