[SERVER-25959] Check whether any mmapv1 options are supplied to other storage engines Created: 05/Sep/16  Updated: 12/Sep/18  Resolved: 18/Aug/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Michael Cahill (Inactive) Assignee: Kim Tao
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-25008 Disallow repairPath with non-mmap sto... Closed
Sprint: Storage 2017-08-21, Storage 2017-09-11
Participants:

 Description   

Follow-on from SERVER-25008:

A more complete solution might be:

  1. move repairpath into MMAPV1Options struct, so that it lives with all the
    mmapv1-specific options, and
  2. enforce all the mmapv1-specific options the same way, not just repairpath.
    E.g., the server should also fail to start up if you use "quotafiles" or
    "nopreallocj" without mmapv1.


 Comments   
Comment by kim.tao [ 18/Aug/17 ]

This will not be fixed, because MMAPv1 is going to be deprecated.

Generated at Thu Feb 08 04:10:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.