[SERVER-77532] Clear drop pending reaper state before re-opening the catalog after rollback to stable Created: 26/May/23 Updated: 29/Oct/23 Resolved: 31/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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: | Execution Team 2023-06-12 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 151 | ||||||||
| Description |
|
Right now we clear the drop pending state after rollback to stable, and re-opening the catalog. During re-opening, we can register internal idents that need to be dropped. But if the internal ident is already registered, we'll hit a fatal assertion. So we need to flip the ordering. What's worse, with the current ordering, is that catalog re-opening can register internal idents to drop, but we clear the state shortly after. These idents would not be dropped until a server restart.
|
| Comments |
| Comment by Githook User [ 31/May/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit b76ba4c151dcec6daf4cfd2c29fadceff355a36a) |
| Comment by Githook User [ 31/May/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |