You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/12/18 01:30:00 UTC

[jira] [Commented] (ARTEMIS-2578) Clarify storage capacity messages

    [ https://issues.apache.org/jira/browse/ARTEMIS-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998725#comment-16998725 ] 

ASF subversion and git services commented on ARTEMIS-2578:
----------------------------------------------------------

Commit 2a452bd7a344c94d25ff2e4d13d84cb3869f4b8d in activemq-artemis's branch refs/heads/master from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2a452bd ]

ARTEMIS-2578 clarify storage capacity messages

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.


> 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: Minor
>          Time Spent: 0.5h
>  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)