[SERVER-29555] Make repair more robust, or optionally error tolerant Created: 12/Jun/17 Updated: 12/Jun/17 Resolved: 12/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chris Kuethe | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When running in repair mode, don't abort the whole server with an assertion failure if one database or collection fails to repair unless absolutely necessary. Instead, move on to the next database. |
| Comments |
| Comment by Chris Kuethe [ 12/Jun/17 ] |
|
Thanks, voted and watching |
| Comment by Kelsey Schubert [ 12/Jun/17 ] |
|
Thank you for the improvement request. This work is being tracked in Kind regards, |