[DOCS-11273] readConcern={level: "majority"} on the inMemory storage engine with writeConcernMajorityJournalDefault: true doesn't offer read-your-writes Created: 31/Jan/18 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: | Judah Schvimer | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| 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 |
|
The docs say "To ensure that a single thread can read its own writes, use "majority" read concern and "majority" write concern against the primary of the replica set.". Since |
| 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! |
| Comment by Judah Schvimer [ 26/Feb/18 ] |
|
Upon further review in BACKPORT-1667, some commits didn't get backported to 3.2 making it so in-memory storage engines do not provide the read-your-own-writes property for read/write concern majority. |
| Comment by Judah Schvimer [ 31/Jan/18 ] |
|
This may be a false alarm. It appears if this is a problem, it is not 3.2 specific. After talking to milkie and max.hirschhorn, inMemory nodes with writeConcernMajorityJournalDefault: true do not count towards the majority, which prevents them from offering read your writes behavior. I'm closing this until we can do more investigation into what the behavior actually is here to document this correctly. |