[SERVER-25008] Disallow repairPath with non-mmap storage engines Created: 11/Jul/16 Updated: 20/Feb/17 Resolved: 05/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Michael Cahill (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, only the MMAPv1 storage engine will acknowledge the --repairPath option when specified. WiredTiger for instance will never check if this option is set or use the option if provided. Specifying repairPath with storage engines other than MMAPv1 should fail. The documentation will be updated to reflect this in |
| Comments |
| Comment by Githook User [ 05/Sep/16 ] |
|
Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}Message: |
| Comment by Daniel Pasette (Inactive) [ 12/Jul/16 ] |
|
Sounds good Michael. Maybe error of any non-mmap engine. |
| Comment by Michael Cahill (Inactive) [ 12/Jul/16 ] |
|
pasette, completely agree: the only way I could see to support repairPath with WiredTiger would be to make a copy of the database, then run the existing repair. I'll take this one. |
| Comment by Daniel Pasette (Inactive) [ 12/Jul/16 ] |
|
I think this might be quite tricky to support with the WiredTiger storage engine. We should immediately fix the documentation that this is only supported on MMAPv1 and error out if attempted with another storage engine. |