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

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

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

ARTEMIS-2246 clarify docs for defaults; change max-disk-usage default


> Documentation for configuration max-disk-usage is inaccurate.
> -------------------------------------------------------------
>
>                 Key: ARTEMIS-2246
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2246
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.6.4
>            Reporter: Leo Provido
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.7.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> During the execution of tests involving sending messages to the System, we 
> observed that the System started blocking messages before the disk is full.
> According to the Configuration Reference 
> ([https://activemq.apache.org/artemis/docs/1.4.0/configuration-index.html]) 
> documentation, the default value of the configuration max-disk-usage is 100. 
> However, we discovered that the actual default value of max-disk-usage is 90. 
> The file inspected is ./etc/broker.xml. Thus, the documentation is deemed 
> inaccurate.
> We have the opinion that severity of this incident is Major because a) the 
> documentation provides an inaccurate piece of information that influences the 
> way we design our mitigation strategies for risks surrounding hardware 
> resources utilization, and b) we don’t necessarily have the bandwidth to 
> review all default configuration values.
> Inaccurate information may cause failure to provide message brokering 
> services despite mitigation strategies being in place.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to