-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
Documentation Request Summary:
If it isn't clear from the ticket description, this ticket disallows --nojournal in the specific case of running WT on a replica set node.
Engineering Ticket Description:
Running WT without journaling will no longer be a supported configuration for a replica set node in 3.6.
Scope of changes:
- relnotes
- 4.0
- 3.6-compat
- 4.0-compat
- nojournal
- source/includes/extracts-manage-journaling.yaml
- source/includes/options-mongod.yaml
- source/includes/wiredtiger-node-nojournal.rst
- storage.journal
- source/includes/options-mongod.yaml
- source/administration/production-notes.txt
- source/includes/options-conf.yaml
- source/core/wiredtiger.txt
- source/reference/connection-string.txt
- writeCOncernmajorityJournalDefault
- source/core/inmemory.txt
- source/core/journaling.txt
- source/includes/extracts-concurrency-consistency-recency.yaml
- source/includes/options-conf.yaml
- source/includes/options-mongod.yaml
- source/reference/replica-configuration
Impact to other docs outside of this product:
none (per Marian search – journaling from OpsMgr/Cloud mgr point back to manual)
MVP:
Resources:
- documents
-
SERVER-30347 Fail startup when running wiredTiger with --nojournal as part of a replica set
- Closed
- related to
-
DOCS-10925 --nojournal option is deprecated for WiredTiger nodes in a replica set.
- Closed