Details
-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
AMQ 7.2.0.GA
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
Description
At the moment we allow for setting the global-max-size upon broker creation which controls the memory that data may consume, however it would also be useful if we could set the max-disk-usage in the same way. It would also then be more obvious why if we log a message stating what the max-disk-usage is set to.
This is especially the case for when the broker is deployed into OpenShift via an immutable image where the broker is created upon deployment. It will provide for an obvious place to recognize a problem and potentially adjust the configuration to avoid it.
Attachments
Issue Links
- is related to
-
ENTMQBR-2369 Doc that max-disk-usage can now be configured at broker creation
- New