You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Barnaby Court (Jira)" <ji...@apache.org> on 2021/01/07 16:26:01 UTC

[jira] [Created] (ARTEMIS-3057) Provide alternative to max-disk-usage to measure by remaining disk free

Barnaby Court created ARTEMIS-3057:
--------------------------------------

             Summary: Provide alternative to max-disk-usage to measure by remaining disk free
                 Key: ARTEMIS-3057
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3057
             Project: ActiveMQ Artemis
          Issue Type: New Feature
          Components: ActiveMQ-Artemis-Native
    Affects Versions: 2.16.0
            Reporter: Barnaby Court
            Assignee: Clebert Suconic


Today we can specify max-disk-usage as a percentage of disk that may be used before blocking the queues. I believe this is done in order to prevent journal corruption. Currently the value can be specified as a percentage which works well for relatively small disks. When working on large systems with many terabytes of storage even specifying 99% is going to result in queues being blocked when there are still many gigabytes of disk space remaining. 

It would be very helpful to have an alternative version of the max-disk-usage that allowed us to specify the threshold below which blocking should be activated. For example, min-disk-available set to something like 500 megabytes or 1 gigabyte before blocking the queues. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)