[SERVER-46253] Rolling back a partially-committed collection creation transaction can cause catalog inconsistencies Created: 19/Feb/20 Updated: 29/Oct/23 Resolved: 26/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Maria van Keulen |
| 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 | ||||||||||||
| Sprint: | Execution Team 2020-02-24, Execution Team 2020-03-09 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 48 | ||||||||||||
| Description |
|
This scenario can cause catalog inconsistencies. Transaction 1 creates collection B The catalog inconsistency results because as we apply the commit of transaction 1, we register collection B in the catalog before finding out that collection A failed to be registered. We do not currently have rollback handling to roll back the registration of collection B. |
| Comments |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria.vankeulen@mongodb.com'}Message: |
| Comment by Githook User [ 24/Feb/20 ] |
|
Author: {'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria.vankeulen@mongodb.com'}Message: |