[SERVER-36540] Improve Session::lock/unlockTxnNumber() Created: 08/Aug/18  Updated: 27/Oct/23  Resolved: 29/Oct/18

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

Current implementation is crude and can only correctly support one call site for lockTxnNumber(), specifically it will be unsafe to call unlock() if lockTxnNumber is called in more than once place because it can unintentionally unlock something it shouldn't.



 Comments   
Comment by Kaloian Manassiev [ 29/Oct/18 ]

Gone away as part of the changes for SERVER-37244.

Comment by Randolph Tan [ 09/Aug/18 ]

Also suggest changing the API so that caller won't mistakenly call unlock when they never called lock (which is the case today)

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