[
https://issues.apache.org/jira/browse/ARTEMIS-3057?focusedWorklogId=878929&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-878929
]
ASF GitHub Bot logged work on ARTEMIS-3057:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Aug/23 20:15
Start Date: 29/Aug/23 20:15
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #3812:
URL:
https://github.com/apache/activemq-artemis/pull/3812#issuecomment-1698063219
@clebertsuconic, I was going by what you said back in December 2021:
> I will merge this right after 2.20 is released...
Issue Time Tracking
-------------------
Worklog Id: (was: 878929)
Time Spent: 7h 50m (was: 7h 40m)
> 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: Broker
> Affects Versions: 2.16.0
> Reporter: Barnaby Court
> Priority: Major
> Labels: easy
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> 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.20.10#820010)
