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 2015/09/15 16:53:46 UTC
[jira] [Commented] (AMQ-5969) Add a configurable threshold property
for disk limit change
[ https://issues.apache.org/jira/browse/AMQ-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745563#comment-14745563 ]
ASF subversion and git services commented on AMQ-5969:
------------------------------------------------------
Commit 4cddd2c015435732b3ff5503160fa87b37154e2b in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4cddd2c ]
https://issues.apache.org/jira/browse/AMQ-5963
Disk limits can now be specified as a percentage of the partition size
that the store is located on. The usual checks of the max size
exceeding the available space will still apply. When using a
percentage, the store can always regrow itself if space becomes
available.
https://issues.apache.org/jira/browse/AMQ-5964
https://issues.apache.org/jira/browse/AMQ-5965
https://issues.apache.org/jira/browse/AMQ-5969
> Add a configurable threshold property for disk limit change
> -----------------------------------------------------------
>
> Key: AMQ-5969
> URL: https://issues.apache.org/jira/browse/AMQ-5969
> Project: ActiveMQ
> Issue Type: Sub-task
> Affects Versions: 5.12.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.13.0
>
>
> There should be a configurable offset/threshold value set to prevent the disk limits from growing to often when only minor changes happen to the disk size. A good default value is probably something like 1 megabyte, but could be configured higher or lower.
> This would mean that the store limit value would only increase when the available space changes by at least the offset value.
> This only applies to growing the store (when using the percent option) because we always want to shrink the store limit if it's too large even if by 1 byte to make sure the configured limit is never higher than the available space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)