Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
-
Sharding
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.
Attachments
Issue Links
- duplicates
-
SERVER-36487 Fail writes to 'config.transactions' for sessions with a transaction in 'prepare'
-
- Closed
-