activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5393) Update disk based limits periodically
Date Tue, 09 Jun 2015 20:38:01 GMT

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

Christopher L. Shannon commented on AMQ-5393:
---------------------------------------------

Good catch with the file not getting cleaned up.  I added some clean up code to my PR to make
sure the test folder and files are cleaned up.  The JUnit Temp folder is nice but I couldn't
use in this case because I would need to give the temp folder a parent directory (the data
store folder) to make sure the test was accurate.  However, I can't guarantee the parent folder
exists before the Temporary folder JUnit Rule runs and it will blow up if the parent folder
is missing, so it was easier to add it to Before/After myself.




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

Mime
View raw message