We recently had a case at a customer where some dead letter queues
retained messages for a long time while messages in all other queues
were short lived. The long lived messages were messages from short lived
queues that were moved to the dead letter queues. This created very
sparsely populated kahadb journals of quite extensive size (~50GB).
In that case it helps to switch to multi kahadb:
See chapter "Automatic Per Destination Persistence Adapter" in
http://activemq.apache.org/kahadb.html.
This creates one kahadb per destination. So you can keep the kahadb size
small without manually deleting the queues regularly. The dead letter
queues of course remain but now are very densely populated so they just
use minimal space.
Christian
On 15.03.2017 08:18, Hidekazu wrote:
Thanks Andreas
The article you introduced me was very helpful to understand the
specification of kahaDB.
I have to say there was a miss-communication among our developer team.
I heard that there was no pending queue in ActiveMQ, however,
There were a lot of pending queue in ActiveMQ and that was the reason kahaDB
journals were never deleted.
I'm sorry.. (but thanks to you, I understood the it well.)
After deleting pending queue in ActiveMQ GUI console, kahaDB journals were
deleted.
Thanks a lot.
Kawai
--
View this message in context:
http://activemq.2283324.n4.nabble.com/The-size-of-KahaDB-doesn-t-seem-to-decrease-tp4723669p4723771.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
