activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Pietrowicz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
Date Tue, 16 Nov 2010 20:53:30 GMT

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

Steve Pietrowicz commented on AMQ-2736:
---------------------------------------

I've been trying to track down a solution to a problem similar to this, and the latest snapshot
of 5.5 doesn't resolve this for me.

This is the scenario I've created:

1) a producer starts sending messages
2) a consumer starts consuming messages, but pauses after 100.
3) db-##.log files start showing up in the tmp_storage directory as expected.   I let the
producer go for a while so a number of db-##.log files are created.
4) the consumer starts consuming messages again. The db-##.log files start disappearing as
they're used up.
5) everything finishes.

Now, if I do:

1) a producer starts sending messages
2) a consumer starts consuming messages, but pauses after 100.
3) db-##.log files start showing up in the tmp_storage directory as expected.   I let the
producer go for a while so that a number of db-##.log files are created.

and kill the consumer and the producer.  The db-##.log files remain, and will not get cleaned
up, even on subsequent invocations of new consumers and producers.  If a new consumer/producer
(as in the first scenario) are created, it all works;  it's just that those old .log files
never get cleaned up.

> KahaDB doesn't clean up old files
> ---------------------------------
>
>                 Key: AMQ-2736
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2736
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.2
>            Reporter: Adrian Trenaman
>            Assignee: Dejan Bosanac
>            Priority: Critical
>             Fix For: 5.5.0
>
>         Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt,
MyKahaDBStore.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message