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 2017/02/14 11:34:41 UTC
[jira] [Commented] (AMQ-6547) mKahaDB: support storeUsage per
filtered instance
[ https://issues.apache.org/jira/browse/AMQ-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865621#comment-15865621 ]
ASF subversion and git services commented on AMQ-6547:
------------------------------------------------------
Commit fad50812af792606efca5653f9b4761e663ac087 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=fad5081 ]
[AMQ-6547] revert mod from AMQ-3143 such that waitForSpace respects child usage, fix test and validate mKahadb blocking send
> mKahaDB: support storeUsage per filtered instance
> -------------------------------------------------
>
> Key: AMQ-6547
> URL: https://issues.apache.org/jira/browse/AMQ-6547
> Project: ActiveMQ
> Issue Type: Improvement
> Components: KahaDB, Message Store
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)