[SERVER-19815] Improved mongod --repair option for WiredTiger Created: 06/Aug/15 Updated: 22/Jun/22 Resolved: 18/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | 4.0.3, 4.1.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael Cahill (Inactive) | Assignee: | Louis Williams |
| Resolution: | Done | Votes: | 37 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Storage NYC 2018-06-18, Storage NYC 2018-09-10, Storage NYC 2018-09-24 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Issue Status as of October 1st, 2018 ISSUE DESCRIPTION AND IMPACT
DIAGNOSIS AND AFFECTED VERSIONS
While these are only some of the most common, most mongod --repair operations that fail to boot the mongod exhibit this issue. REMEDIATION AND WORKAROUNDS FIX VERSIONS Original descriptionThe repair loop should be more forgiving about failures such as missing files and deal with collections or indexes missing from the catalog with a big warning message. |
| Comments |
| Comment by Kalyan Kumar A [ 16/Jul/20 ] |
|
Thanks, I have similar issue with 4.0.19 version, are the above fixes applicable in my version, can you please update. Thanks |
| Comment by Louis Williams [ 21/Sep/18 ] |
|
All changes described in my previous comment have been backported to 4.0, with the exception of the removal of the repairDatabase command. This command's behavior remains unchanged in 4.0. |
| Comment by Louis Williams [ 18/Sep/18 ] |
|
Starting mongod with --repair on a WiredTiger data directory now handles and recovers from the following scenarios:
Additionally, --repair has the following new behavior:
|
| Comment by Kelsey Schubert [ 04/Jul/17 ] |
|
Hi ccornel, This issue would be best addressed in a new SERVER ticket. Would you please open one so we can investigate? Thank you, |
| Comment by Carlos Cornel [ 04/Jul/17 ] |
|
Hi I hope someone can help please... my files Regards Carlos |
| Comment by Alexander Gorrod [ 08/Jan/17 ] |
That is correct - you need the other files from the MongoDB database directory. Those files contain important metadata information that is necessary for WiredTiger to know which data is where, and how to access the data in those files. If the files in your database directory have become corrupted, there are several steps to take to get back online. The following options are listed in priority order:
The goal of this ticket is to move the line between options 3 and 4, so that automatic repair is possible in more cases. |
| Comment by Muhammad Haris NP [ 08/Jan/17 ] |
|
Once I have .wt files, I should be able to recreate the database. Now there is no way I can recreate the database from the .wt files if I don't have the other files like WiredTiger .. |
| Comment by Stefan Rogin [ 23/Jun/16 ] |
|
Important feature, to ignore corrupt collections, when recovering a database with many collections and have only a tiny/recoverable one corrupt or out of alignment. |
| Comment by Asya Kamsky [ 01/Jun/16 ] |
|
Users have requested ability to start mongod to either manually or automatically to "drop" entities that don't have files/directories present. |
| Comment by Alexander Gorrod [ 19/Oct/15 ] |
|
Thanks david.hows. The categorization is taking shape now. Can you think of a way to test the different scenarios? Preferably as part of the regular MongoDB test suite. |
| Comment by David Hows [ 14/Oct/15 ] |
|
Database files missing
Database files corrupted
Index files missing
Index files corrupted
MongoDB catalogue metadata may be out of alignment with the WT files on disk
|