[SERVER-33529] Ban $isolated and $atomic in local snapshot reads and multistatement transactions Created: 27/Feb/18  Updated: 27/Oct/23  Resolved: 22/Mar/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-30005 remove $isolated/$atomic option Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

These types of updates/deletes take strong locks, which could cause a deadlock when the transaction waits to acquire a WT ticket when unstashing resources. These modifiers are also deprecated.

It may not be necessary to ban these modifiers from local snapshot reads, since we intend to ban readConcern level snapshot from writes outside of multistatement transactions as part of SERVER-33412.



 Comments   
Comment by James Wahlin [ 22/Mar/18 ]

This work is no longer required as $isolated and $atomic have been removed from the server.

Comment by Eric Milkie [ 12/Mar/18 ]

Going to implement SERVER-30005 instead.

Generated at Thu Feb 08 04:33:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.