[SERVER-76109] Allow --repair to startup a server with invalid index specs in the catalog Created: 14/Apr/23 Updated: 29/Oct/23 Resolved: 11/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Erin Liang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution NAMR Team 2023-06-26, Execution NAMR Team 2023-07-10, Execution NAMR Team 2023-07-24 | ||||||||
| Participants: | |||||||||
| Description |
|
mongod fasserts during startup if we have any index with an invalid index spec such us containing unknown fields. Even --repair fasserts and does not perform any repair. We should change this behavior to allow --repair attempt to repair an invalid index spec. |
| Comments |
| Comment by Githook User [ 11/Jul/23 ] |
|
Author: {'name': 'Erin Liang', 'email': 'erin.liang@mongodb.com', 'username': 'erl-ang'}Message: |