[
https://issues.apache.org/jira/browse/AMQ-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated AMQ-5964:
----------------------------------------
Description:
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.
was: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 to some maximum value in the same task if
disk space becomes available again.
Summary: Add an option to increase disk based limits if space is
available for percentage case (was: Add an option to increase disk based
limits if space is available)
> 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)
