[
https://issues.apache.org/jira/browse/ARTEMIS-2246?focusedWorklogId=195917&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-195917
]
ASF GitHub Bot logged work on ARTEMIS-2246:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Feb/19 20:20
Start Date: 07/Feb/19 20:20
Worklog Time Spent: 10m
Work Description: jbertram commented on issue #2541: ARTEMIS-2246 clarify
docs for defaults; change max-disk-usage default
URL: https://github.com/apache/activemq-artemis/pull/2541#issuecomment-461581392
This was replaced by #2544.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 195917)
Time Spent: 2h 50m (was: 2h 40m)
> 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: 2h 50m
> 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)
