activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-2736) KahaDB doesn't clean up old files
Date Thu, 23 Jun 2011 14:03:48 GMT

    [ https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053867#comment-13053867
] 

Gary Tully commented on AMQ-2736:
---------------------------------

Auto consolidation would be a nice enhancement. Can you open a new issue to track that.

As you know, you can also reduce the journal data file size to reduce the overall disk usage
in this case.

One other thought, using a camel route, you can easily consume and re-submit messages so that
they are moved to the current journal data file. Have a look at the route from the dlq back
the the original destination for inspiration. https://issues.apache.org/jira/browse/AMQ-2710.
The idea would be to periodically fire a consumer, using quarts, that removes and adds messages.
See the test that pulls the original destination from the message.

http://svn.apache.org/viewvc/activemq/trunk/activemq-camel/src/test/resources/org/apache/activemq/camel/CamelRedeliveryTest-context.xml?view=markup
http://svn.apache.org/viewvc/activemq/trunk/activemq-camel/src/test/java/org/apache/activemq/camel/CamelRedeliveryTest.java?view=markup

> KahaDB doesn't clean up old files
> ---------------------------------
>
>                 Key: AMQ-2736
>                 URL: https://issues.apache.org/jira/browse/AMQ-2736
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.2
>            Reporter: Adrian Trenaman
>            Assignee: Gary Tully
>            Priority: Critical
>             Fix For: 5.5.0
>
>         Attachments: AMQ-2736.zip, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java,
amq-2987-testcase.patch, amq-2987.patch
>
>
> Over time, we're seeing that kahadb doesn't clean up old journal files. As a result,
we eventually run out of disk space, or rather, we hit our usage limits and our producers
are slowed down by the producer flow control mechanism. Others have experienced this problem
too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3C27502591.post@talk.nabble.com%3E)
> For now, we're moving back to the old amqPersistenceStore. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message