[DOCS-7847] Clarify WiredTiger journal files are not deleted on clean shutdown Created: 10/May/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kelsey Schubert | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
|
Since this is a significant difference in behavior between MMAPv1 and WiredTiger, it may be worth highlighting in the documentation: https://docs.mongodb.com/v3.2/core/journaling/#journaling-and-the-wiredtiger-storage-engine When journaling with WiredTiger, there should always be at least one log file, and these log files will remain after a clean shutdown. After restarting, MongoDB will enter a recovery stage and will use any log records it needs. The log files are still required in the case of a clean shutdown since MongoDB is not initially aware of whether it suffered an unclean shutdown. After recovery, the archive will run and remove all non-essential files. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |