You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/07/06 16:21:11 UTC
[jira] [Commented] (ARTEMIS-581) Add setting to control global disk
usage
[ https://issues.apache.org/jira/browse/ARTEMIS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364548#comment-15364548 ]
clebert suconic commented on ARTEMIS-581:
-----------------------------------------
Makes sense...
Although I would always fail when that disk limit is hit. It would make understanding and configuration easier for users. Controlling what to do in case of a disk full, would give users too many options and would complicate user's decision.
Would anyone be contrary to always fail the Send or Transaction in case the configured disk limit is hit?
> 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
> Reporter: Lionel Cons
>
> 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)