[SERVER-76741] Split-prepare transactions are aborted before reserving abort oplog entry Created: 02/May/23 Updated: 29/Oct/23 Resolved: 03/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Lingzhi Deng | Assignee: | Wenbin Zhu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||
| Sprint: | Repl 2023-05-15 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 135 | ||||||||||||||||||||
| Description |
|
Primary aborts the split-prepared transactions before it reserves the abort oplog entry. This is a bug as it violates the assumption noted in the comment. This bug would enable a sequence like the following - Let's say we have Txn1 and Txn2 that write to the same set of documents: In this case, secondaries would see prepare of Txn2 before abort of Txn1, resulting in prepare conflicts when applying Txn2. |
| Comments |
| Comment by Githook User [ 04/May/23 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: (cherry picked from commit 9cf95efcbd37df83bcd9af4593e79c51ea4062ea) |
| Comment by Githook User [ 03/May/23 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: |