[
https://issues.apache.org/jira/browse/AMQ-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Chiarello updated AMQ-6516:
-----------------------------------
Description:
When ActiveMQ starts, it tries to adjust its store limits based on the total
available space on the disk. However, if the store is not empty, the current
Usage is not taken into account.
*Scenario*
Store Limit = 20 Go, disk Size = 25 Go, current Store Usage = 15 Go
When restarting ActiveMQ, available disk space is 25 -15 = 10 Go, and the
broker automatically resize the store limit from 20 to 10 Go. However, the
store is already 15 Go, and thus effectively full (store usage = 150% reported
in the console).
Starting logs:
{noformat}
WARN | Store limit is 20240 mb (current store usage is 0 mb). The data
directory: (...)\data\kahaDB only has 12387 mb of usable space. - resetting to
maximum available disk space: 12387 mb
{noformat}
Logs report a current usage of 0 Mb whereas there is more than 10 Go of data in
the store. When connecting a debugger to ActiveMQ, I noticed that the current
store usage is computed _before_ the persistence adapter is configured (this is
done by the post construct in
{{XBeanBrokerService#ensureSystemUsageHasStore()}}, and thus always report '0'.
Tested on 5.14.1, but the same behavior was already noticed on 5.12.x and
5.13.x versions
was:
When ActiveMQ starts, it tries to adjust its store limits based on the total
available space on the disk. However, if the store is not empty, the current
Usage is not taken into account.
*Scenario*
Store Limit = 20 Go, disk Size = 25 Go, current Store Usage = 15 Go
When restarting ActiveMQ, available disk space is 25 -15 = 10 Go, and the
broker automatically resize the store limit from 20 to 10 Go. However, the
store is already 15 Go, and thus effectively full (store usage = 150% reported
in the console).
Starting logs:
{noformat}
WARN | Store limit is 20240 mb (current store usage is 0 mb). The data
directory: (...)\data\kahaDB only has 12387 mb of usable space. - resetting to
maximum available disk space: 12387 mb
{noformat}
Logs report a current usage of 0 Mb whereas there is more than 10 Go of data in
the store. When connecting a debugger to ActiveMQ, I noticed that the current
store usage is computed _before_ the persistence adapter is configured (this is
done by the post construct in
{{XBeanBrokerService#ensureSystemUsageHasStore()}}, and thus always report '0'.
> Wrong StoreUsageLimit computed at startup
> -----------------------------------------
>
> Key: AMQ-6516
> URL: https://issues.apache.org/jira/browse/AMQ-6516
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.14.1
> Reporter: Laurent Chiarello
>
> When ActiveMQ starts, it tries to adjust its store limits based on the total
> available space on the disk. However, if the store is not empty, the current
> Usage is not taken into account.
> *Scenario*
> Store Limit = 20 Go, disk Size = 25 Go, current Store Usage = 15 Go
> When restarting ActiveMQ, available disk space is 25 -15 = 10 Go, and the
> broker automatically resize the store limit from 20 to 10 Go. However, the
> store is already 15 Go, and thus effectively full (store usage = 150%
> reported in the console).
> Starting logs:
> {noformat}
> WARN | Store limit is 20240 mb (current store usage is 0 mb). The data
> directory: (...)\data\kahaDB only has 12387 mb of usable space. - resetting
> to maximum available disk space: 12387 mb
> {noformat}
> Logs report a current usage of 0 Mb whereas there is more than 10 Go of data
> in the store. When connecting a debugger to ActiveMQ, I noticed that the
> current store usage is computed _before_ the persistence adapter is
> configured (this is done by the post construct in
> {{XBeanBrokerService#ensureSystemUsageHasStore()}}, and thus always report
> '0'.
> Tested on 5.14.1, but the same behavior was already noticed on 5.12.x and
> 5.13.x versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
