[DOCS-12048] Update Transaction Docs: How to avoid stale reads in transactions Created: 11/Sep/18 Updated: 30/Oct/23 Resolved: 06/Nov/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alyson Cabral (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 14 weeks, 1 day ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
DescriptionOnly writes trigger conflicts in transactions. This is true for all implementations of snapshot isolation across databases. Let's add a section to the transactions documentation to explain how to avoid stale reads in certain operations by doing a findAndModify or update to that document in the transaction in addition to the read. Scope of changeshttps://docs.mongodb.com/manual/core/transactions/index.html https://docs.mongodb.com/manual/core/write-operations-atomicity/index.html Impact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 06/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 06/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |