activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Carpella (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (AMQ-2736) KahaDB doesn't clean up old files
Date Mon, 06 Jun 2011 15:53:00 GMT

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

Martin Carpella edited comment on AMQ-2736 at 6/6/11 3:51 PM:
--------------------------------------------------------------

I am seeing this or a similar issue on a 5.5.0 broker as well, log files are not being deleted.
I now deleted all queues, but I am still seeing the checkpoint task "DEBUG | queue://a.deleted.queue
expiring messages .." in the logs.

I stopped ActiveMQ afterwards and restartet it, after I deleted all queues and still the space
being occupied.

During the restart, even after I deleted all queues, I had:
{code}
DEBUG | XA Transaction new/begin : XID:1096044365:3137322e31372e312e352e746d31353531373030333432:3137322e31372e312e352e746d37313330363334
DEBUG | Ack for non existent subscription in recovery, ack:MessageAck {commandId = 66898301,
responseRequired = false, ackType = 2, consumerId = ID:CLIENT-001-40008-1306310098527-2:5:10553821:1,
firstMessageId = e041a486-8c88-3855-304e-4c9eac0f85b1:0:61129:61129, lastMessageId = e041a486-8c88-3855-304e-4c9eac0f85b1:0:61129:61129,
destination = queue://a.deleted.queue, transactionId = XID:1096044365:3137322e31372e312e352e746d31353531373030333432:3137322e31372e312e352e746d37313330363334,
messageCount = 1, poisonCause = null}
{code}

After the restart, all the space was still occupied and log-files were never deleted. But
at least no more expiry entries for the now deleted queues any more.

KahaDB is 3 according to startup logs. Unfortunately I cannot provide steps to reproduce for
5.5.0 at the moment and the store in question is several GB in size and contains sensitive
information I cannot share. 

Should I re-open this issue or a file this as a new issue?

      was (Author: mcarpella):
    I am seeing this or a similar issue on a 5.5.0 broker as well, log files are not being
deleted. I now deleted all queues, but I am still seeing the checkpoint task "DEBUG | queue://a.deleted.queue
expiring messages .." in the logs.

I stopped ActiveMQ afterwards and restartet it, after I deleted all queues and still the space
being occupied.

{code}
During the restart, even after I deleted all queues, I had:
DEBUG | XA Transaction new/begin : XID:1096044365:3137322e31372e312e352e746d31353531373030333432:3137322e31372e312e352e746d37313330363334
DEBUG | Ack for non existent subscription in recovery, ack:MessageAck {commandId = 66898301,
responseRequired = false, ackType = 2, consumerId = ID:CLIENT-001-40008-1306310098527-2:5:10553821:1,
firstMessageId = e041a486-8c88-3855-304e-4c9eac0f85b1:0:61129:61129, lastMessageId = e041a486-8c88-3855-304e-4c9eac0f85b1:0:61129:61129,
destination = queue://a.deleted.queue, transactionId = XID:1096044365:3137322e31372e312e352e746d31353531373030333432:3137322e31372e312e352e746d37313330363334,
messageCount = 1, poisonCause = null}
{code}

After the restart, all the space was still occupied and log-files were never deleted. But
at least no more expiry entries for the now deleted queues any more.

KahaDB is 3 according to startup logs. Unfortunately I cannot provide steps to reproduce for
5.5.0 at the moment and the store in question is several GB in size and contains sensitive
information I cannot share. 

Should I re-open this issue or a file this as a new issue?
  
> 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