Why did my KahaDB index file grow to several GB and does not shrink even when there are no messages left on any queues?
Issue
We noticed the KahaDB index file db.data has grown to several GB in size and does not even get reduced when there is no backlog of messages on the broker.
ls -l ./kahadb/
-rw-r--r--. 1 test test 33554432 Jul 12 11:20 db-1610.log
-rw-r--r--. 1 test test 5262196736 Jul 12 11:20 db.data
-rw-r--r--. 1 test test 32836096 Jul 12 11:20 db.redo
-rw-r--r--. 1 test test 8 Jul 5 07:21 lock
Why is db.data so big while there are no messages stored (anymore)?
Will A-MQ shrink this file at some point?
Environment
- JBoss A-MQ 6.x
- KahaDB persistence store
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.