[SERVER-81879] startupRecoveryForRestore can drop tables whose catalog write is not yet checkpointed Created: 04/Oct/23 Updated: 15/Nov/23 Resolved: 15/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0, 4.4.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2023-11-13, Execution Team 2023-11-27 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Description |
|
When using startupRecoveryForRestore we advance the oldest timestamp during startup oplog recovery, as described in |
| Comments |
| Comment by Gregory Noma [ 15/Nov/23 ] |
|
This is describing a specific case of the same issue described in |
| Comment by Gregory Noma [ 15/Nov/23 ] |
|
This should already be fixed in versions newer than 5.0 thanks to |
| Comment by Steven Vannelli [ 05/Oct/23 ] |
|
This should be investigated alongside We think the implementation used in |