[
https://issues.apache.org/jira/browse/AMQ-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583523#comment-14583523
]
Timothy Bish edited comment on AMQ-5393 at 6/12/15 2:49 PM:
------------------------------------------------------------
I've pushed the PR to master, for now I've left the default as disabled. My
feeling it to leave it off by default for now until it gets used a big to judge
any unintended side effects the only the fly changes might have. We can of
course revisit later and decide to enable it out of the box.
We should probably document the new configuration setting and what it does, I'm
not sure we have a page on the Wiki with a canonical listing of the
configuration options available in the Broker element now that I look for it.
was (Author: tabish121):
I've pushed the PR to master, for now I've left the default as disabled. My
feeling it to leave it off by default for now until it gets used a big to judge
any unintended side effects the only the fly changes might have. We can of
course revisit later and decide to enable it out of the box.
> Update disk based limits periodically
> -------------------------------------
>
> Key: AMQ-5393
> URL: https://issues.apache.org/jira/browse/AMQ-5393
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.10.0
> Reporter: Dejan Bosanac
> Fix For: 5.12.0
>
>
> At the moment, we set store and temp limits at broker startup based on the
> configuration and available space. It's possible that other artefacts such as
> logs can reduce available disk space so that our limits does not have effect.
> It'd be good to periodically check for the usable space left and adjust
> limits accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
