Details
-
Improvement
-
Resolution: Duplicate
-
Minor - P4
-
None
-
None
-
None
-
None
-
Security 2021-06-28
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).
Attachments
Issue Links
- duplicates
-
SERVER-47198 SIGUSR1 can cause MongoDB process crash
-
- Closed
-