[SERVER-71637] Repair does not handle case where the WT table for an index is missing Created: 28/Nov/22 Updated: 05/Dec/22 Resolved: 28/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| 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 | ||||||||
| Participants: | |||||||||
| Description |
|
Startup repair will fail if the WT table for an index is missing. I can reproduce the scenario by using the wt command-line tool to drop a table for an index and then start up the server with --repair. Note that deleting the file from the data directory is not sufficient to reproduce this problem. The table must be dropped from the WT metadata itself. |