Kahadb message store size too big

[jimspence]

Hi All,

We are currently using Fuse, an embedded broker and kahadb persistence.

This is an extract from our activemq-broker.xml (virtually default settings)

We are currently experiencing problem with the size of our kahadb journal message store increasing at an alarming rate, with a huge list of db-XXXX.log files.

Our queues are not all completely clear so I can understand that we may have kahadb journal files that are still required as they hold currently queued message information, but our 200 messages or so shouldnt require 7gigs for of files surely?

We are using FUSE 4.4 and embedded activemq version 5.5.

Any guidance would be appreciated.

[davsclaus]

To my understanding Fuse MB 5.6 has improved kahadb, so it have a more intelligent  distribution of log files, which in overall should reduce the file size.

Gary could possible elaborate a bit more about this.

[jimspence]

Thanks for the prompt reply Claus. 2 further questions then...

1. I guess Activemq 5.6 will be integrated into the next version of Fuse. When will that be?

2. In the mean time is there any sort of work around that I can reduce the kahadb storage size? We have about 200 messages across multiple queues. Could we archive those messages off somewhere, clear down the store and copy them back using something like Hermes?

Cheers, Jim

[jimspence]

Sorry...just bouncing this one....any advice anyone?

[dejanb_dejan]

Hi,

here's a description of Multi KahaDB persistence adapter, which will be available in the next release, so that you can set different stores for high-volume and low-volume destinations

http://activemq.apache.org/kahadb.html#KahaDB-Multi%28m%29kahaDBpersistenceadapter

As for the tool for defragmenting current store, there is one talked about here

http://fusesource.com/issues/browse/MB-756

Please backup your store before doing any modification with the tool.

Regards,

Dejan

Edited by: dejanb on Oct 27, 2011 5:33 PM