[SERVER-62873] Startup repair does not handle orphaned index catalog entries Created: 21/Jan/22 Updated: 02/May/23 Resolved: 02/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||
| Backport Requested: |
v6.0, v5.0
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2023-02-20, Execution Team 2023-05-01 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Startup repair has logic to handle orphaned collection catalog entries, i.e. a catalog entry referencing a collection that is not known to the storage engine. However, it does not appear to handle the same scenario for indexes. |
| Comments |
| Comment by Fausto Leyva (Inactive) [ 02/May/23 ] |
|
Since we are backporting |
| Comment by Dianna Hohensee (Inactive) [ 25/Apr/23 ] |
|
Putting this aside in favor of |
| Comment by Gregory Noma [ 09/Jun/22 ] |
|
I closed this as Won't Do, in favor of |
| Comment by Louis Williams [ 08/Jun/22 ] |
|
gregory.noma@mongodb.com can we close this ticket since we completed |
| Comment by Louis Williams [ 22/Feb/22 ] |
|
This ticket describes a feature of --repair, but I also filed |