[DOCS-10925] --nojournal option is deprecated for WiredTiger nodes in a replica set. Created: 20/Oct/17  Updated: 29/Oct/23  Resolved: 14/Nov/17

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 3.6.0-rc0

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Steve Renaker (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-30760 Add startup warning if running wiredT... Closed
Related
related to DOCS-10928 Replica set nodes running with --nojo... Closed
related to SERVER-31635 deprecate running WiredTiger replica ... Closed
related to DOCS-11032 Clarify disabling journaling in Wired... Closed
is related to DOCS-11224 Docs for SERVER-30347: Fail startup w... Closed
Participants:
Days since reply: 6 years, 13 weeks ago
Epic Link: DOCS: 3.6 Server
Story Points: 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



 Comments   
Comment by Githook User [ 15/Nov/17 ]

Author:

{'name': 'Steve Renaker', 'username': 'steveren', 'email': 'steve.renaker@mongodb.com'}

Message: DOCS-10925: added relevant note to 3.6-compatibility
Branch: master
https://github.com/mongodb/docs/commit/e7df31f03a02577a6f8897a5372cb3f6e15f21d4

Comment by Githook User [ 15/Nov/17 ]

Author:

{'name': 'Steve Renaker', 'username': 'steveren', 'email': 'steve.renaker@mongodb.com'}

Message: DOCS-10925: --nojournal option is deprecated for WiredTiger nodes in a replica set
Branch: master
https://github.com/mongodb/docs/commit/247178fca891fbff317b6e754c2a1e07644aaa49

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