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 GitHub Bot (JIRA)" <ji...@apache.org> on 2015/06/09 21:47:00 UTC

[jira] [Commented] (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=14579471#comment-14579471 ] 

ASF GitHub Bot commented on AMQ-5393:
-------------------------------------

GitHub user cshannon opened a pull request:

    https://github.com/apache/activemq/pull/110

    https://issues.apache.org/jira/browse/AMQ-5393

    Adding a property called schedulePeriodForDiskUsageCheck which can be set
    to a time period to periodically check disk usage limits and adjust if the amount of 
    disk space has been reduced.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cshannon/activemq AMQ-5393

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/110.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #110
    
----
commit 24385ce97f208ee710616249f33b66c0af14dcd3
Author: Christopher L. Shannon (cshannon) <ch...@gmail.com>
Date:   2015-06-09T19:40:16Z

    https://issues.apache.org/jira/browse/AMQ-5393
    
    Adding a property called schedulePeriodForDiskUsageCheck which can be set
    to a time period to periodically check disk usage limits and adjust if
    the amount of disk space has been reduced.

----


> 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)