activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hank.X.Hua (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-4677) LevelDB can't move all message data logs that are no longer used
Date Thu, 24 Oct 2013 06:14:02 GMT

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

Hank.X.Hua edited comment on AMQ-4677 at 10/24/13 6:12 AM:
-----------------------------------------------------------

In ActiveMQ 5.9.0,leveldb store can't cleans up all as the data is consumed from the store
when send messages faster than the rate of consumption.Stop sending messages, the message
is consumed when finished, there are many DataLog not cleared.


was (Author: hank.hua):
In ActiveMQ 5.9.0,leveldb store can't cleans up all as the data is consumed from the store
when send messages faster than the rate of consumption.

> LevelDB can't move all message data logs that are no longer used
> ----------------------------------------------------------------
>
>                 Key: AMQ-4677
>                 URL: https://issues.apache.org/jira/browse/AMQ-4677
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store
>    Affects Versions: 5.8.0
>         Environment: OS:
> Windows 7 Professional
> MQ:
> <persistenceAdapter>
>     <levelDB directory="D:/temp/levelDB"/>
> </persistenceAdapter>
>            Reporter: Hank.X.Hua
>            Assignee: Timothy Bish
>             Fix For: 5.x
>
>         Attachments: AMQ4677Test.java
>
>
> Producers and consumers of a single thread to send and consume 50,000 messages, each
message size is 600K, capacity of 28G or so;
> Problem: after the message is sent and consumption, there are 7G about the file is not
clear.
> By the way, kahaDB have an attribute "cleanupInterval", Why levelDB without this?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message