[SERVER-57690] Allow log rotation via SIGUSR1 to fail without killing the server Created: 14/Jun/21  Updated: 14/Jun/21  Resolved: 14/Jun/21

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

Type: Improvement Priority: Minor - P4
Reporter: Sara Golemon Assignee: Sara Golemon
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-47198 SIGUSR1 can cause MongoDB process crash Closed
Sprint: Security 2021-06-28
Participants:

 Description   

Currently, if log rotation fails (e.g. due to destination file already existing), then the server will always abort even though it could theoretically continue with the old log destination just fine.

Report the failure to rotate in the log, but do not invariant (unless the cause was actually something critical).


Generated at Thu Feb 08 05:42:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.