[
https://issues.apache.org/jira/browse/QPID-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8004:
-----------------------------
Description:
When "Maximum Number of Rolled Files" is configured on FileLogger and the
number of rolled files reaches the maximum, the broker can scans file system 60
times submitting a scan task every 5 seconds.
{{RollingPolicyDecorator.ScanTask}} takes into account only file names to
detect new rolled files. Thus, when the number of rolled files reaches the
maximum on the FileLogger with {{SizeTriggeringPolicy}} rollover policy, the
names of the rollover files remain the same as old files are deleted and
remaining files are renamed to match {{fileName + ".%i"}} where {{%i}} is a
file index starting from {{0}}. {{RollingPolicyDecorator.ScanTask}} can be
improved to take into consideration last modification or creation time to
detect the new rolled over files correctly.
was:
When "Maximum Number of Rolled Files" is configured on FileLogger and the
number of rolled files reaches the maximum, the broker can scans file system 60
times submitting a scan task every 5 seconds.
{{RollingPolicyDecorator.ScanTask}} takes into account only file names to
detect new rolled files. Thus, when the number of rolled files reaches the
maximum on the FileLogger with {{SizeTriggeringPolicy}} rollover policy, the
names of the rollover files remain the same as old files are deleted and
remaining files are renamed to match {{fileName + ".%i"}} where {{%i}} is a
file index starting from {{0}}. {{RollingPolicyDecorator.ScanTask}} can be
improved to take into consideration last modification or creation time to
detect the rolled over files correctly.
Summary: [Broker-J] RollingPolicyDecorator excessively scans file
system for rolled over files. (was: [Broker-J] RollingPolicyDecorator
execively scans file system for rolled over files.)
> [Broker-J] RollingPolicyDecorator excessively scans file system for rolled
> over files.
> ---------------------------------------------------------------------------------------
>
> Key: QPID-8004
> URL: https://issues.apache.org/jira/browse/QPID-8004
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-broker-7.0.0, qpid-java-6.1.4, qpid-java-6.0.8
> Reporter: Alex Rudyy
>
> When "Maximum Number of Rolled Files" is configured on FileLogger and the
> number of rolled files reaches the maximum, the broker can scans file system
> 60 times submitting a scan task every 5 seconds.
> {{RollingPolicyDecorator.ScanTask}} takes into account only file names to
> detect new rolled files. Thus, when the number of rolled files reaches the
> maximum on the FileLogger with {{SizeTriggeringPolicy}} rollover policy, the
> names of the rollover files remain the same as old files are deleted and
> remaining files are renamed to match {{fileName + ".%i"}} where {{%i}} is a
> file index starting from {{0}}. {{RollingPolicyDecorator.ScanTask}} can be
> improved to take into consideration last modification or creation time to
> detect the new rolled over files correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]