[SERVER-73340] Drop abandoned idents at startup using the stable timestamp Created: 26/Jan/23 Updated: 29/Oct/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2023-02-06 | ||||||||
| Participants: | |||||||||
| Description |
|
The idents may be needed for reads between oldest and the stable timestamp. Defer the drop using the reaper until the stable timestamp at startup is outside the time window we may perform reads on. |
| Comments |
| Comment by Githook User [ 30/Jan/23 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: With point-in-time catalog lookups, the index could have existed between the oldest and the stable timestamp. To allow reads in this window we defer the index drop until the stable timestamp using the two-phase drop reaper. |