[SERVER-49340] Add repair mode to validate for startup --repair Created: 07/Jul/20 Updated: 29/Oct/23 Resolved: 14/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Shin Yee Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||
| Sprint: | Execution Team 2020-07-13, Execution Team 2020-07-27 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Add a mode to validate internally that repairs data. This should be used by startup --repair before attempting to rebuild indexes. The CollectionValidation::validate() function will accept a RepairData enum flag to allow it to fix certain problems that do not require a full index rebuild. This new “repair mode” will be used by startup repair in repairCollections to avoid rebuilding indexes in certain corruption cases. If there were validation errors and they were all fixed, validate will report valid: false in ValidateResults and a new member repairStatus: OK |
| Comments |
| Comment by Githook User [ 17/Sep/21 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: (cherry picked from commit 674b8eb) |
| Comment by Githook User [ 14/Jul/20 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com'}Message: |