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.