activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-4211) Spooling to disk an a per destination usage limit basis rather than on shared usage
Date Fri, 07 Dec 2012 12:57:20 GMT
Gary Tully created AMQ-4211:
-------------------------------

             Summary: Spooling to disk an a per destination usage limit basis rather than
on shared usage
                 Key: AMQ-4211
                 URL: https://issues.apache.org/jira/browse/AMQ-4211
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Broker
    Affects Versions: 5.7.0
            Reporter: Gary Tully


Currently the filepending message cursor spools to disk when the system usage  memory limit
gets to 70% - the highWaterMark.
Why is this not based on the destination limit? 

I think we need to investigate using the destination limit for the filepending message cursor
so that it is trivially easy to get spooling to disk happen for a destination. 
ie: set a policyEntry memory limit of 1mb on a destination and send it 1.2mb of messages and
it will purge to disk and free up the 1mb.

To achieve this today, the 'system' memory limit needs to be 1mb and this effects all destinations
and pfc (b/c of the shared parent).

note: if the destination does not have a limit, then the destination is limited by the parent
system usage, so the global effect can be the same as before.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message