[SERVER-49842] Startup repair should rebuild indexes when validate index inconsistencies exceed the memory limit Created: 23/Jul/20 Updated: 29/Oct/23 Resolved: 25/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-09-07 |
| Participants: |
| Description |
|
If the memory usage of gathering index inconsistencies exceeds the memory limit, we skip gathering missing/extra index entires in the second phase of validation. This results in us skipping the path to fix up indexes in Ensure that when validate repair mode exceeds its memory limit, startup repair still rebuilds indexes. |
| Comments |
| Comment by Githook User [ 25/Aug/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |