You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a FileLogWriterState is created, it sometimes rotate_output_file_to_date but does not call remove_or_zip_too_old_logfiles. The latter is only called when an existing _rCURRENT overflows. Therefore when a downstream program is run repeatedly, but doesn't generate enough log messages to trigger mount_next_linewriter_if_necessary in a single run, old rCURRENT messages can accumulate indefinitely in the log directory.
The text was updated successfully, but these errors were encountered:
When only a small amount of log messages are generated in the lifetime of a program, the procedure to clean up previous log files is not triggered, so log files keep accumulating. When the clean-up procedure is triggered in any single run that generates enough log messages, the old log files are removed to comply with Cleanup::KeepLogFiles(u64).
When a
FileLogWriterState
is created, it sometimesrotate_output_file_to_date
but does not callremove_or_zip_too_old_logfiles
. The latter is only called when an existing_rCURRENT
overflows. Therefore when a downstream program is run repeatedly, but doesn't generate enough log messages to triggermount_next_linewriter_if_necessary
in a single run, oldrCURRENT
messages can accumulate indefinitely in the log directory.The text was updated successfully, but these errors were encountered: