[DOCS-4594] Journal files behaviour description is misleading Created: 01/Jan/15 Updated: 30/Oct/23 Resolved: 07/Dec/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 12 weeks, 1 day ago |
| Description |
|
http://docs.mongodb.org/manual/core/journaling/#journal-files
MongoDB does not actively delete the journal files as the highlighted phrasing suggests. Instead, old journal files lie around until a new one is required. Given that the current one is guaranteed to still be in use at the time a new one is needed, at least two will persist at all times on any instance that has seen reasonable activity in it's current running lifetime. The two latest journal files will stay around forever while the mongod is running even if you stop all writes. Only when a new journal file is required, are old ones (that are available) recycled for use as the new one. |
| Comments |
| Comment by Githook User [ 24/Nov/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 24/Nov/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |