The index grows based off the amount of data it tracks in the journal, but doesn't shrink. This means if you had a lot of data in your journal at some point (several gigabytes, etc) then the index would have grown in size with enough page files to keep track of all of the data. This is usually not an issue because the index size generally stabilizes at some point relative to the work load of the broker. If you really want to shrink it the only way right now is to stop the broker, delete the index and restart so it does a replay and rebuilds the index but the size would just grow again as messages flow.
On Mon, Jan 23, 2017 at 8:06 PM, Scorpio <n...@xiangjiabao.com> wrote: > Hi, All, > > In my activemq instance, I find that the kahadb index file is larger than > the journal file. > > As far as I know, /db.data/ is the meta store, index for the journal file, > which should means it is much smaller than the journal file. However, it > does not look like that. The index file seems to keep growing while the > journal file is rotated. Do I miss something? Thanks. > > Log attached: > root@host:~/run/apache-activemq-5.13.1/data/kahadb# du * -sh > 16M db-16.log > 1.2G db.data > 3.2M db.redo > 4.0K lock > root@host:~/run/apache-activemq-5.13.1/data/kahadb# > > Kind regards, > Scorpio > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/kahadb-index-file-larger-than-journal-file-tp4721284.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
