activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5964) Add an option to increase disk based limits if space is available for percentage case
Date Tue, 15 Sep 2015 14:53:45 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745561#comment-14745561
] 

ASF subversion and git services commented on AMQ-5964:
------------------------------------------------------

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 an option to increase disk based limits if space is available for percentage case
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-5964
>                 URL: https://issues.apache.org/jira/browse/AMQ-5964
>             Project: ActiveMQ
>          Issue Type: Sub-task
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.13.0
>
>
> Besides dynamically shrinking the maximum disk space used based on available space (both
periodically and on start up), we could also add the option increase the disk space usage
back to the percentage limit set if space frees up in the future.
> For now, this is only really doable with the percentage based case as described in AMQ-5965
unless some rework was done to the limit configuration.  This is because currently the disk
check resets the limit to a lower value if it's too high so we don't track the original value
anymore to regrow too.  However, for the percentage base the original limit percent size will
still be known so this is possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message