ramanathan1504 commented on PR #4159:
URL: https://github.com/apache/logging-log4j2/pull/4159#issuecomment-4815419572
@OpenZYK
1.`Redundant for Load Leveling`: A simple `[0, max]` uniform distribution
(PR
#4071) already spreads the `I/O` spikes perfectly; forcing a minimum
delay
provides no extra infrastructure benefit.
2.`API Maintenance Burden`: Introducing a second parameter (min) pollutes
core
public APIs with overloaded constructors and builder attributes that we
must
maintain indefinitely.
3.`Thread & Memory Retention`: High minimum delays `(e.g., 20+ minutes)`
will
unnecessarily block execution threads and keep file/action states in the
`JVM`
heap, risking thread starvation and memory bloat.
4.`Delayed Disk Cleanup`: Forcing a minimum wait time keeps large,
uncompressed
log files on the disk longer, defeating the goal of rapid disk-space
recovery.
5.`Configuration Overhead`: A single `maxCompressionDelaySeconds`
parameter is
simpler for users to configure and achieves the exact same operational
outcome.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
