[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:
Backports
Duplicate
is duplicated by SERVER-71637 Repair does not handle case where the... Closed
Problem/Incident
causes SERVER-71571 build index fail , DB crash ,can not ... Closed
Related
related to SERVER-63865 Handle missing index idents during st... Closed
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 SERVER-63865, this ticket is no longer necessary. 

Comment by Dianna Hohensee (Inactive) [ 25/Apr/23 ]

Putting this aside in favor of SERVER-63865 backports.

Comment by Gregory Noma [ 09/Jun/22 ]

I closed this as Won't Do, in favor of SERVER-63865.

Comment by Louis Williams [ 08/Jun/22 ]

gregory.noma@mongodb.com can we close this ticket since we completed SERVER-63865 instead?

Comment by Louis Williams [ 22/Feb/22 ]

This ticket describes a feature of --repair, but I also filed SERVER-63865 so that indexes in this situation can be dropped in standalone mode instead, which I think is a simpler and less expensive operation.

Generated at Thu Feb 08 05:56:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.