You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2014/03/12 04:03:47 UTC
[jira] [Updated] (AMQ-4832) Broker limits store space, not taking
into account what it's already using
[ https://issues.apache.org/jira/browse/AMQ-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated AMQ-4832:
---------------------------------
Fix Version/s: 5.9.1
> Broker limits store space, not taking into account what it's already using
> --------------------------------------------------------------------------
>
> Key: AMQ-4832
> URL: https://issues.apache.org/jira/browse/AMQ-4832
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Reporter: Matthew Walker
> Assignee: Gary Tully
> Fix For: 5.9.1, 5.10.0
>
> Attachments: 0001-Store-limit-check-current-usage-and-disk-free-space.patch
>
>
> https://issues.apache.org/jira/browse/AMQ-4638 sets the usage limit of a store to only the available disk space. It does not take into account that the store itself is using space on the disk.
> In our environment the store was taking 30 GB of space and there was 17 GB free on disk. Therefore, on startup the store was limited to 17 GB; where it should have been limited to 47 GB. Because of this, by design, no new message can be added to the queue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)