[DOCS-9923] storage.repairPath only applies to MMAPv1 Created: 20/Feb/17  Updated: 23/Aug/17  Resolved: 10/Aug/17

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 3.3.14

Type: Bug Priority: Major - P3
Reporter: James Kovacs Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-25008 Disallow repairPath with non-mmap sto... Closed
Participants:
Days since reply: 6 years, 51 weeks, 2 days ago

 Description   

https://docs.mongodb.com/manual/reference/configuration-options/#storage.repairPath states:

Not available for mongod instances that use the in-memory storage engine.

However MongoDB 3.4 with WiredTiger produces this error message when run with the repairpath option:

[initandlisten] exception in initAndListen: 40311 Cannot start server. The command line option '--repairpath' is only supported by the mmapv1 storage engine, terminating 

This behaviour was added in MongoDB 3.3.14 as per SERVER-25008. Based on HELP-2295, repairpath has always been ignored by storage engines other than MMAPv1, but previously we silently ignored the option.


Generated at Thu Feb 08 07:59:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.