[SERVER-15234] mongod logs "old journal file will be removed" even when it isn't Created: 12/Sep/14 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, MMAPv1 |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin Pulo | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
In Journal::removeUnneededJournalFiles() the server logs when it's about to call removeOldJournalFile(). The log message is "old journal file will be removed". However, if journal file preallocation is in use, then removeOldJournalFile() might recycle and rename the journal file, rather than removing it. This means that the log message can be confusing, since it suggests that file deletion is occurring, when in fact this does not happen. |
| Comments |
| Comment by Githook User [ 31/Mar/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 07/Mar/16 ] |
|
The file is logically removed as it is no longer treated as a journal file. The fact it's renamed instead of deleted is an optimization. |