[
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027211#comment-15027211
]
Ralph Goers commented on LOG4J2-435:
------------------------------------
Robert,
Are you not familiar with cron? If I use a cron string of "0 0 0 * * ?" the
delete operation would only be triggered every day at midnight. No need to
check every second. One of the issues we have with the current
TimeBasedTriggeringPolicy is that it requires log events to occur to trigger
the file rollover. Trying to detect changes in the configuration files and
whether to roll over files while processing log events adds extra overhead to
the processing of each and every log event. As of 2.5 all of that will now
happen in separate threads managed by the scheduler.
Yes, it is a question of performance. We are moving to things happening when
the time event occurs and we are stopping polling on every log event whether we
should be doing it or not.
In a future release I plan on deprecating the TimeBasedTriggeringPolicy.
> Feature request: auto-delete older log files
> ---------------------------------------------
>
> Key: LOG4J2-435
> URL: https://issues.apache.org/jira/browse/LOG4J2-435
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Arkin Yetis
> Assignee: Remko Popma
> Labels: Rollover
> Fix For: 2.5
>
> Attachments: LimitingRolloverStrategy.java, SizeParser.java
>
>
> Original description:
> {quote}
> DefaultRolloverStrategy max attribute only applies if you have a %i in the
> file pattern. This request is to enhance DefaultRolloverStrategy or another
> appropriate component to allow a max number of files limit to apply across
> days/months/years when a filePattern includes a date pattern.
> {quote}
> ----
> One of the most requested features is to add the ability to Log4j to "clean
> up" older log files. This usually means deleting these files, although it
> could also mean moving them to a different location, or some combination of
> these.
> Users have different requirements for selecting the files to clean up. A
> common request is the ability to keep the last X number of log files. This
> works well if rollover is only date based but may give undesired results with
> size based rollover.
> Another factor to consider is that the directory containing the log files may
> contain the log files for multiple appenders, or even files unrelated to
> logging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
