activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-581) Add setting to control global disk usage
Date Wed, 15 Nov 2017 22:20:01 GMT


ASF subversion and git services commented on ARTEMIS-581:

Commit 19c6f2d5c4171518e0933a3a6abfc54453c95565 in activemq-artemis's branch refs/heads/master
from [~gaohoward]
[;h=19c6f2d ]

NO-JIRA Added test coverage for broker paging with unlimited memory

This test starts 2 servers and send messages to
a queue until it enters into paging state. Then
it changes the address max-size to -1, restarts
the 2 servers again and consumes all the messages.
It verifies that even if the max-size has changed
all the paged messages will be depaged and consumed.
No stuck messages after restarting.

The tests is there to guard a case where messages
won't be depaged on server restart after the max-size
is changed to -1. This issue has been fixed into
master along with the fix for ARTEMIS-581, particularly
the changes to the method PagingStoreImpl.getMaxSize().

> Add setting to control global disk usage 
> -----------------------------------------
>                 Key: ARTEMIS-581
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>    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

View raw message