[ https://issues.apache.org/jira/browse/ARTEMIS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421214#comment-15421214 ]
clebert suconic commented on ARTEMIS-581: ----------------------------------------- Actually, we can only do fail.. no block. opening this to block means we would be bound to flow control options. And if a client disabled flow control we would blow up disk anyways. So, the only possible way is to fail (send an exception and rollback TX). > Add setting to control global disk usage > ----------------------------------------- > > Key: ARTEMIS-581 > URL: https://issues.apache.org/jira/browse/ARTEMIS-581 > Project: ActiveMQ Artemis > Issue Type: Improvement > Affects Versions: 1.3.0 > Reporter: Lionel Cons > Assignee: clebert suconic > Priority: Blocker > Fix For: 1.4.0 > > > AFAIK, there is no way to prevent Artemis from using too much space on the > disk (with paged messages). > Disk space, just like memory space, is limited and Artemis should detect when > it is about to use too much space and act accordingly (i.e. DROP, FAIL...). > ActiveMQ 5.x does allow controlling disk usage via its {{storeUsage}} and > {{tempUsage}} settings in {{systemUsage}}. > Could Artemis also use a global disk setting to limit its disk usage? -- This message was sent by Atlassian JIRA (v6.3.4#6332)