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

logRotate should not fassert when rename target exists

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Logging
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: