[
https://issues.apache.org/jira/browse/ARTEMIS-2578?focusedWorklogId=361072&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-361072
]
ASF GitHub Bot logged work on ARTEMIS-2578:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Dec/19 19:15
Start Date: 17/Dec/19 19:15
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #2921: ARTEMIS-2578
clarify storage capacity messages
URL: https://github.com/apache/activemq-artemis/pull/2921
This is a surprisingly large change just to fix some log messages, but
the changes were necessary in order to get the relevant data to where it
was being logged. The fact that the data wasn't readily available is
probably why it wasn't logged in the first place.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 361072)
Remaining Estimate: 0h
Time Spent: 10m
> Clarify storage capacity messages
> ---------------------------------
>
> Key: ARTEMIS-2578
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2578
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When large disks (e.g. 1TB) are used with the default {{max-disk-usage}}
> (i.e. {{90}}) it can be confusing when the broker reports that disk capacity
> is low and starts blocking producers because there is still a lot of disk
> space left (e.g. 100GB using the values above). The log message should
> include the {{max-disk-usage}} as well as the total capacity and capacity
> remaining.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
