[
https://issues.apache.org/jira/browse/AMQ-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814359#comment-13814359
]
Ben O'Day commented on AMQ-4093:
--------------------------------
seems like this should be categorized as severe unless there is a known
workaround. how are others dealing with this issue?
> Auto Consolidation of Database Files to reduce DB footprint size
> ----------------------------------------------------------------
>
> Key: AMQ-4093
> URL: https://issues.apache.org/jira/browse/AMQ-4093
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Message Store
> Affects Versions: 5.6.0
> Reporter: Stephanie Miotke
> Priority: Minor
>
> This issue is being spawned from a comment in AMQ-2736:
> "I have a queue that holds onto a message every once in a while due to bad
> formatting or what-have-you (not something I can immediately correct). Since
> KahaDB requires the need to retain the full contents of the DB file while one
> message persists, it will cause the file system to grow dramatically if you
> alter the default kahaDB file size at all. With a DB file of 96 megs each
> I've eaten up almost 5 gigs of disk space in 34 pending messages all less
> than 2000 bytes each.
> I'm going to begin auto purging the offending queue (since we don't require
> those messages), however it would be preferred to have some automatic process
> possibly automatically consolidate the DB once its reached a pre-configured
> limit?"
> So, I'd like to officially request some sort of consolidation or 'garbage
> collection' of kahadb files when the storage footprint reaches a
> preconfigured limit, allowing the ActiveMQ system to clean itself up and
> prevent overflowing disk space with pending messages that may never get
> processed.
> Please let me know if you have any questions or need any further information.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.1#6144)
