[DOCS-12969] 4.2 won't start with MMAPv1 options Created: 20/Aug/19  Updated: 30/Oct/23  Resolved: 02/Oct/19

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Renato Riccio Assignee: Andrew Feierabend (Inactive)
Resolution: Fixed Votes: 0
Labels: docs-onboarding-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 4 years, 19 weeks ago
Epic Link: DOCSP-1769
Story Points: 0.1

 Description   

Description

Before 4.2 MMAPv1 options used with WT were just ignored.

In 4.2 the server won't start if MMAPv1 options are used:

Error parsing command line: unrecognised option '--smallfiles'
try '/bin/4.2.0/mongod --help' for more information

We should document that in the release notes

Scope of changes

  • Add a blurb to the 4.4 release notes on MMAPv1 removal. Spitballing:

"4.4 mongod or mongos cannot start with MMAPv1 options specified to the command line or configuration file "

  • Add blurb to 4.0 -> 4.2 upgrade notes reminding users to remove MMAPv1 options from the command line or configuration file as part of upgrade
    • Upgrade note needs to be in master and 4.0.

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Andrew Feierabend (Inactive) [ 02/Oct/19 ]

Provided messaging to advise removing MMAPv1 options from WiredTiger deployments, with prominent warnings that these options prevent WiredTiger deployments on 4.2 from starting.

Generated at Thu Feb 08 08:06:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.