[DOCS-15467] Investigate changes in SERVER-55208: Remove support for nojournal Created: 06/Jul/22 Updated: 13/Nov/23 Due: 23/Sep/22 Resolved: 21/Sep/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Alison Huh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 8 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-21764 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Original Downstream Change Summary The --nojournal option has been completely removed, so this should be reflected in the documentation. Additionally, the intermediate step starting up mongod with --nojournal when changing the WT journal compressor is not required, only a clean shutdown and startup is required. The step was "required" due to a bug fixed by https://www.mongodb.com/docs/manual/tutorial/manage-journaling/#change-wiredtiger-journal-compressor Description of Linked TicketDetermine the potential use cases for the nojournal option on the WT storage engine and investigate the potential deprecation of the option |
| Comments |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'Alison Huh', 'email': '112565127+ajhuh-mdb@users.noreply.github.com', 'username': 'ajhuh-mdb'}Message:
|
| Comment by Githook User [ 21/Sep/22 ] |
|
Author: {'name': 'Alison Huh', 'email': '112565127+ajhuh-mdb@users.noreply.github.com', 'username': 'ajhuh-mdb'}Message:
|
| Comment by Education Bot [ 06/Jul/22 ] |
|
Fix Version updated for upstream |