[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:
Related
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: SERVER-15234 Better log message on reusing/deleting MMAPv1 journal files
Branch: master
https://github.com/mongodb/mongo/commit/a53618a1099199e8fbd3e66996826a26528444d5

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.

Generated at Thu Feb 08 03:37:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.