https://bz.apache.org/bugzilla/show_bug.cgi?id=69595
--- Comment #4 from Vijay <[email protected]> --- (In reply to Remy Maucherat from comment #3) > I don't see the point of this feature. Allowing individual daily files > allows doing the removal job of old ones *after some weeks*, in a clean way. > So what's the point of having intra day rotations, besides the "great" > justifications a LLM makes ? If the file is too big, well, you still should > not delete it ... Hi @Remy Maucherat, Thanks for the feedback — that’s a fair question. The main motivation for this enhancement is not to replace existing date-based rotation, but to provide an additional safeguard in environments where disk capacity is constrained. In modern deployments (especially Docker/Kubernetes), logs are often written to ephemeral or size-limited volumes. Under high traffic, a single day's access log can grow large enough to exhaust available disk space before the next date-based rotation occurs. This can lead to operational issues such as: application disruption due to disk exhaustion container restarts or pod eviction While external log rotation tools can handle this, they are not always present or consistently configured across environments. This proposal aims to provide an optional, backward-compatible mechanism to limit log file growth and avoid such failure scenarios. Happy to adjust the approach or drop it if this is considered out of scope for Tomcat. Thanks! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
