[
https://issues.apache.org/jira/browse/ARTEMIS-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312445#comment-17312445
]
Clebert Suconic commented on ARTEMIS-3214:
------------------------------------------
[~erwindon] as a matter of fact.. I already do the check I thought it was
needed.. .when you mentioned messages not gong away, I had a De Ja Voux and I
thought I needed such thing.. but I implemented that a few years ago.. I just
didn't remember it.
I added a few more notes on the user's discussion... make sure all the messages
are expired.. if you have just one message hanging not expired, no messages
would be de-paged unless you consume or expire every reference in memory.
if you have a bug... I would like to see it... You could either send me a test
case.. a print-data (./artemis data print) might help if you can't reproduce
it on a reliable test.. but could it in your system)
> 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)
