[
https://issues.apache.org/jira/browse/AMQ-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916349#comment-13916349
]
Ben O'Day commented on AMQ-4832:
--------------------------------
this should be backported to a 5.9.X release since 5.10.0 hasn't been
released...its a major bug
> 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.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.1.5#6160)
