[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: |
|
||||||||
| 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 |