[SERVER-36699] Direct modifications to config.transactions can potentially bump txnNumber even when in prepared state Created: 16/Aug/18  Updated: 06/Dec/22  Resolved: 16/Aug/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: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-36487 Fail writes to 'config.transactions' ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

When a transaction transitions to prepared state, it is not allowed to bump to txnNumber. This is achieved by using a lock on the txnNumber. However, there is a loop hole where it is possible to directly modify the config.transactions document which causes the in-memory structure to become invalidated and load from storage.



 Comments   
Comment by Judah Schvimer [ 16/Aug/18 ]

Is this not covered by SERVER-36487?

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