Increasing the storage usage limit should not cause any index corruption. You
generally need a restart for the storage usage limit setting to go into effect.
The temp usage is a separate setting and separate usage bucket. Temp space us
used for non-persistent messages to ’swap’ when memory
Would an increase of the storageUsage to 225GB from 150GB cause and index
corruption? A message in the activemq.log indicated that there wasn’t
enough storage to use the 225GB setting? Any advice is helpful. The
tempstorage setting is at 300MB…
On 2022/12/01 20:49:31 Matt Pavlovich wrote:
>
Hello Wendell-
You may have kahadb fragmentation caused by messages sitting in queues that
have not been consumed. Check any DLQ or other queues that do not get consumed
and work to clean them up. Even if you move them to another queue and then back
to their original queue you will clear up
Hello, I am showing AMQ Store Percent usage at 86% my khahadb folder is
registering at 87GB is this normal for it to be this size, and is there a
way for us to mitigate the size due to our directory being at 256GB and we
dont want to run into space issues?
ActiveMQ 5.1.3.1 version
Java 1.8..0
