[
https://issues.apache.org/jira/browse/ARTEMIS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470222#comment-15470222
]
Christopher L. Shannon commented on ARTEMIS-581:
------------------------------------------------
[~clebertsuconic], Thanks for adding this, I think this is a pretty critical
feature to be able to limit the space used and is something I (and probably
many others) rely on in the 5.x broker.
Also, 5.x now supports a couple of other features with disk usage limits which
I added recently and I think would be useful here too. One is defining the max
disk usage in terms of a percentage of the partition instead of a hard limit.
The second is dynamically shrinking/expanding the max limit based on available
space. For example, if the limit is set at 50 GB but some other process writes
data to the partition causing there to be less space available than 50 GB (such
as log files) the max will shrink (and it can expand again if space is cleared
up, etc). I use both of these settings all of the time and it is very helpful.
If no one else gets to it I can take a look at adding them as a PR at some
point when I get some time.
> Add setting to control global disk usage
> -----------------------------------------
>
> Key: ARTEMIS-581
> URL: https://issues.apache.org/jira/browse/ARTEMIS-581
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.3.0
> Reporter: Lionel Cons
> Assignee: clebert suconic
> Priority: Blocker
> Fix For: 1.4.0
>
>
> AFAIK, there is no way to prevent Artemis from using too much space on the
> disk (with paged messages).
> Disk space, just like memory space, is limited and Artemis should detect when
> it is about to use too much space and act accordingly (i.e. DROP, FAIL...).
> ActiveMQ 5.x does allow controlling disk usage via its {{storeUsage}} and
> {{tempUsage}} settings in {{systemUsage}}.
> Could Artemis also use a global disk setting to limit its disk usage?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
