[
https://issues.apache.org/jira/browse/ARTEMIS-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292227#comment-17292227
]
Clebert Suconic commented on ARTEMIS-3148:
------------------------------------------
First Artemis will compact messages only leaving messages that are active.
Second, if a destination has too many messages you start to use a secondary
storage called Paging. On paging you have one folder per address.
> ActiveMQ Artemis mkahadb migration
> ----------------------------------
>
> Key: ARTEMIS-3148
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3148
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: ActiveMQ-Artemis-Native
> Environment: IA64 HP-UX (actual and possible target for artemis)
> X64 ReadHat Linux (Possible target for artemis)
> 11 ActiveMQ with 10 000 persisted queues ~1000000 messages per day
> I can't post on the list anymore
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> Reporter: Terrien Jean-Yves
> Assignee: Clebert Suconic
> Priority: Major
>
> Hello
> We have a system with ActiveMQ which manages a few thousand queues.
> We were faced with a dificulty. If on an instance of ActiveMQ 1 persisted
> queue does not have a consumer, one message is enough in this queue for the
> size of the KahaDB database to increase significantly. Indeed a message not
> consumed in one of the queues of the base prevents the system from freeing
> space for all queues on this database. And we are hiding millions of
> messages. Except with so many tails this is a common situation. To avoid this
> we used mkahaDB. Thus only the queue without a consumer is impacted. The
> other queues can free up space.
> We are considering switching to Artemis. But I don't find any information on
> this specific point in the documentation.
> Won't the new journal clog the filesystem?
> Where can I find the documentation to ensure that in the event of a consumer
> suspension, all messages consumed in other queues will be deleted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
