Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-57690

Allow log rotation via SIGUSR1 to fail without killing the server

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Security 2021-06-28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            sara.golemon@mongodb.com Sara Golemon (Inactive)
            Reporter:
            sara.golemon@mongodb.com Sara Golemon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: