[
https://issues.apache.org/jira/browse/ARTEMIS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471022#comment-15471022
]
clebert suconic commented on ARTEMIS-581:
-----------------------------------------
There are two limits I added:
- global-max-size, which is based on the memory used (I mean.. it's an estimate
on how much each Message and Reference is using in memory).
That will kick in paging (as it's configured by default now) or any other
policy chosen (block, drop, fail or page).
- Global-disk-usage
Here is a percentage of the disk. by default now I have set to 90% (on the
created broker). Here we can only block producers (if the protocol allows it),
or fail the connection (close it) if the protocol doesn't allow it.
> 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)
