[DOCS-14954] [Manual] Consider documenting safe ways to achieve serializability with snapshot isolation Created: 24/Nov/21 Updated: 30/Oct/23 Resolved: 24/May/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | proactive | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 37 weeks ago |
| Description |
|
Snapshot isolation is prone to anomalies like Write-skew. Customers who want to use mongodb but are sensitive to write skew can still use snapshot isolation with various techniques, such as turning reads into writes or synchronizing on an individual document. We should consider if we want to document these workarounds to show that MongoDB can work in these wider use cases. This is similar to how we used to document how to achieve linearizability with findAndModify |
| Comments |
| Comment by Ashley Brown [ 24/May/23 ] |
|
Closing per discussion in comments. Thanks, everyone! |
| Comment by Ashley Brown [ 23/May/23 ] |
|
Hi judah.schvimer@mongodb.com, I just wanted to circle back with you on this older request. I have a couple of questions:
Thanks! |
| Comment by Judah Schvimer [ 24/Nov/21 ] |
|
We also should write Server tests for any recommendations we make here to ensure they do in fact avoid the anomalies we're claiming they do. |