[SERVER-29559] Don't crash the server when a database is missing Created: 12/Jun/17 Updated: 29/Jul/17 Resolved: 22/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris Kuethe | Assignee: | Mark Agarunov |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1) create a database in directory per db mode |
||||||||
| Participants: | |||||||||
| Description |
|
Recently a hard system crash corrupted one of my databases. While I'm trying to figure out which database is corrupt and in need of repair, and to prevent unnecessary repairs to a clean database I'd like to just move it out of the way. Unfortunately that causes an assertion failure. This doesn't seem like a good reason to take down the whole mongod when the other databases could still be perfectly usable. |
| Comments |
| Comment by Mark Agarunov [ 22/Jun/17 ] |
|
Hello chris.kuethe@gmail.com, Thank you for the report. Looking over this, I believe that the underlying changes needed for this are the same as those in Thanks, |