[
https://issues.apache.org/jira/browse/ARTEMIS-3057?focusedWorklogId=680798&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-680798
]
ASF GitHub Bot logged work on ARTEMIS-3057:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Nov/21 12:27
Start Date: 12/Nov/21 12:27
Worklog Time Spent: 10m
Work Description: gemmellr commented on pull request #3812:
URL: https://github.com/apache/activemq-artemis/pull/3812#issuecomment-967073678
> I got `BUILD SUCCESS` with `mvn -Pdev install -Derrorprone`. Not sure if
it's the same with the Github workflow. Please help activate the workflow.
>
I cant approve the workflow here, but you can run it in your own fork
regardless by enabling the actions there, at e.g
https://github.com/haanhvu/activemq-artemis/actions. Then if you push to a
branch which is not already in use for a PR then only your fork will run the
workflow, and you can check the results etc there. Then you can raise a PR when
ready (or update an existing branch already used for an open PR, e.g this one).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 680798)
Time Spent: 6.5h (was: 6h 20m)
> 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: 6.5h
> 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.1#820001)
