activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4677) LevelDB can't move all message data logs that are no longer used
Date Wed, 14 Aug 2013 14:10:49 GMT

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

Timothy Bish commented on AMQ-4677:
-----------------------------------

LevelDB works quite a bit differently from KahaDB.  Compaction occurs in a much more lazy
manner however you can force a compaction by acquiring the LevelDB MBean and calling the compact
method.  
                
> 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
>             Fix For: 5.x
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message