[
https://issues.apache.org/jira/browse/ARTEMIS-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4700.
-------------------------------------
Resolution: Duplicate
> Support address-level disk limit
> --------------------------------
>
> Key: ARTEMIS-4700
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4700
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Justin Bertram
> Priority: Major
>
> Currently ActiveMQ Artemis only restricts normal messages from paging at the
> address level using {{page-limit-bytes}}, and whenever any address exceeds
> this limit we are able to block producers from sending messages to the
> address by setting the {{page-full-policy}} to {{FAIL}}.
> However, this {{page-limit-bytes}} does not cover the {{large-messages}}
> directory in the {{data}} directory due to which there is no track for large
> messages. If any consumer for a queue is down for sometime for which large
> messages are being sent, the storage is getting full impacting other
> customers hosted in the broker. Ideally it should only impact the particular
> tenant.
> We have {{max-disk-usage}} in place, but it's at global level and impacting
> other customers if disk usage is beyond this limit. Could you please check if
> there is any parameter to restrict large messages. We tested and seems the
> destination parameter "Persistent Size" is the sum of the disk used by
> paging, large messages, journals and bindings, but I don't see any
> restriction based on this parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
