You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2015/06/11 19:11:01 UTC
[jira] [Comment Edited] (AMQ-5393) Update disk based limits
periodically
[ https://issues.apache.org/jira/browse/AMQ-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582232#comment-14582232 ]
Christopher L. Shannon edited comment on AMQ-5393 at 6/11/15 5:10 PM:
----------------------------------------------------------------------
I updated the PR with optimized tests. The last two tests I couldn't use Wait.waitFor because the condition doesn't change (the sizes are supposed to stay the same) but I cut down on the sleep time because it was unnecessarily long. All tests should now run at least twice as fast as before.
was (Author: christopher.l.shannon):
I updated the PR and optimized tests. The last two tests I couldn't use Wait.waitFor because the condition doesn't change (the sizes are supposed to stay the same) but I cut down on the sleep time because it was unnecessarily long. All tests should now run at least twice as fast as before.
> 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)