[SERVER-35630] Missing or corrupt data files should cause MongoDB to exit with an error message to run repair Created: 15/Jun/18 Updated: 29/Oct/23 Resolved: 25/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | Storage NYC 2018-07-16, Storage NYC 2018-07-30 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In any of the following cases during startup, MongoDB should exit with the same error message requiring the user to run --repair. The current behavior is a crash with no helpful information.
|
| Comments |
| Comment by Githook User [ 14/Sep/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: (cherry picked from commit 3deba1b701332ad9afb6e722db928ca98714ea87) |
| Comment by Githook User [ 25/Jul/18 ] |
|
Author: {'username': 'xy24', 'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com'}Message: |
| Comment by Xiangyu Yao (Inactive) [ 19/Jul/18 ] |
As according to the conversation with kay.kim, I am going to re-use http://dochub.mongodb.org/core/repair. |
| Comment by Xiangyu Yao (Inactive) [ 19/Jul/18 ] |
|
I think we should include a dochub link to the page about "--repair" in the error message to illustrate the cases and results after repair. |