Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.14.0
-
None
Description
mKahaDB allows multiple journals to be use, with differing QOS. However the broker storeUsage is shared across all instances.
It would be great to have a storeUsage per kahaDB instance such that particular destinations can be restricted to a subset of the available disk space while others are unlimited.
In other words, have diskUsage in the mix as a QOS metric.
Attachments
Issue Links
- is related to
-
AMQ-3143 JMX attribute change doesn't affect store usage
- Resolved