Bug 452141 - Provide means to limit brokers memory use
Provide means to limit brokers memory use
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
All Linux
urgent Severity medium
: 1.0.1
: ---
Assigned To: Gordon Sim
Kim van der Riet
Depends On:
Blocks: 459250
  Show dependency treegraph
Reported: 2008-06-19 12:03 EDT by Gordon Sim
Modified: 2008-10-06 15:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-06 15:08:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gordon Sim 2008-06-19 12:03:31 EDT
In the simplest case we should just issue session exceptions when client attempt
to do things that would push the broker above a given limit.
Comment 1 Gordon Sim 2008-07-10 04:47:51 EDT
Moving target to 1.1 as we don't yet have a good solution for this.
Comment 3 Gordon Sim 2008-07-17 11:13:49 EDT
Initial suggested solution is as follows:

On startup broker determines the available system memory. The default policy on
any queue for which an explicit policy is not set is to not go above a certain
percentage of this (else flow to disk or throw exception as usual).
Comment 4 Gordon Sim 2008-07-25 09:36:56 EDT
Fixed by r679462.
Comment 5 Gordon Sim 2008-08-15 04:03:45 EDT
Fix involves applying a fixed size (but configurable) default policy for queues (--default-queue-policy). Once the total message data on the queue reaches that limit, further publications will be either flushed to disk (if the queue is durable) or failed.
Comment 7 Frantisek Reznicek 2008-09-10 04:26:06 EDT
RHTS test MRG_Messaging/qpid_queue_policy_bz452141_bz456667 proves that queue policies (queue max message count and queue byte size) are implemented and tested. (ON_QA->VERIFIED)
Comment 9 errata-xmlrpc 2008-10-06 15:08:12 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.