logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47575] GZipping large files stops logging
Date Wed, 05 Aug 2009 03:50:33 GMT

--- Comment #2 from Derek Libby <derek.libby@gmail.com> 2009-08-04 20:50:32 PDT ---
We had accumulated a large log file approximately 10GB in size.  Just using
gzip on the (Linux) box in question required about 2 minutes to compress the
file.  The rollover check happens then next time a logging event comes in and
the check interval has been exceeded which for our purposes meant essentially
the next time the check interval was exceeded (1000ms I believe).  All of our
threads then blocked until the GZip operation was complete causing the system
to stop responding for that interval.

I didn't actually move the block in question, but the only time it makes sense
to block on lastRolloverAsyncAction is when its value is about to change which
will not be until the next log roll is required which was midnight in our

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message