[
https://issues.apache.org/jira/browse/ARTEMIS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422444#comment-15422444
]
Lionel Cons commented on ARTEMIS-581:
-------------------------------------
FWIW, ActiveMQ 5.x has several parameters (such as {{sendFailIfNoSpace}} or
{{sendFailIfNoSpaceAfterTimeout}}) to control what happens when resources are
exhausted, see http://activemq.apache.org/producer-flow-control.html.
IMHO, configuring the response (block, fail...) should be independent from the
cause (disk full, single queue full...) and should very likely be protocol
specific since not all protocols support flow control.
If the response cannot be configured, I would prefer to first try to block (if
the protocol allows it) and then fail if blocking does not work.
> Add setting to control global disk usage
> -----------------------------------------
>
> Key: ARTEMIS-581
> URL: https://issues.apache.org/jira/browse/ARTEMIS-581
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> 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)
