[SERVER-19729] logRotate should not fassert when rename target exists Created: 03/Aug/15  Updated: 03/Aug/15  Resolved: 03/Aug/15

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16821 Do not abort server when receiving mu... Closed
Related
Participants:

 Description   

Performing a logRotate operation on mongoD will rename the rotated file, appending a timestamp in the following format: <YYYY>-<mm>-<DD>T<HH>-<MM>-<SS>

If log rotation is run twice within a given second, mongod will fatally assert on the second iteration. It fails in trying to rename the log file to an existing name.

Rather than fatally assert in this scenario we should either make the second rotation attempt a no-op (logging an error to the current log) or allow the rotation to succeed under a expanded name.



 Comments   
Comment by Ramon Fernandez Marina [ 03/Aug/15 ]

Duplicate of SERVER-16821.

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