Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Small
-
0.2
Description
WiredTiger nodes in a replica set should not be run with the --nojournal option.
--nojournal is deprecated within a replica set and won't work once the recover to timestamp code is turned on (most likely in 3.8).
https://docs.mongodb.com/manual/reference/program/mongod/index.html#cmdoption-nojournal
https://docs.mongodb.com/manual/tutorial/manage-journaling/index.html#disable-journaling
Attachments
Issue Links
- documents
-
SERVER-30760 Add startup warning if running wiredTiger with --nojournal as part of a replica set
-
- Closed
-
- is related to
-
DOCS-11224 Docs for SERVER-30347: Fail startup when running wiredTiger with --nojournal as part of a replica set
-
- Closed
-
- related to
-
DOCS-10928 Replica set nodes running with --nojournal should have writeConcernMajorityJournalDefault set to false.
-
- Closed
-
-
SERVER-31635 deprecate running WiredTiger replica set nodes with journaling disabled
-
- Closed
-
-
DOCS-11032 Clarify disabling journaling in WiredTiger
-
- Closed
-