You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Erwin Dondorp (Jira)" <ji...@apache.org> on 2021/03/31 10:43:00 UTC
[jira] [Closed] (ARTEMIS-3214) apply automatic page-in when all
messages in a queue have expired
[ https://issues.apache.org/jira/browse/ARTEMIS-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erwin Dondorp closed ARTEMIS-3214.
----------------------------------
Resolution: Cannot Reproduce
[~clebertsuconic] [~gtully]
I'm trying to reproduce the problem that I reported.
But it does not reproduce; and all messages are properly expired.
I will close this issue and work on a repeater first...
> apply automatic page-in when all messages in a queue have expired
> -----------------------------------------------------------------
>
> Key: ARTEMIS-3214
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3214
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> When there are many messages in a queue, the messages are (by default) paged.
> However, when all these messages expire (given that a TTL is set), and there are no consumers, only the in-memory messages are removed. This leaves all paged messages in their on-disk state, thus preventing further actual message expiry.
> Is it possible to add a function where messages are paged-in more often? e.g. when the in-memory part of the queue is empty during an expiry-sweep. This is useful even when only one chunk is paged-in to not keep the expiry-thread unreasonably busy. This will eventually lead to the actual expiry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)