Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of chirino@gmail.com designates
 209.85.212.43 as permitted sender)
MIME-Version: 1.0
Sender: chirino@gmail.com
In-Reply-To: <20110729073946.21ef.abe10f7e5afbbb3a79ce619739541149@cern.ch>
References: <20110729073946.21ef.abe10f7e5afbbb3a79ce619739541149@cern.ch>
Date: Fri, 29 Jul 2011 13:14:42 -0400
Message-ID: 
 <CAGZ-RDKjQ2YmWe5S43qY9D2yeM9NX1uwHB03PZN=svaiXgqc0A@mail.gmail.com>
Subject: Re: Per-destination queue quota
From: Hiram Chirino <hiram@hiramchirino.com>
To: Lionel Cons <lionel.cons@cern.ch>
Cc: dev@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Yes,

Please open up an issue for it.

Regards,
Hiram

FuseSource
Web: http://fusesource.com/


On Fri, Jul 29, 2011 at 1:50 AM, Lionel Cons <lionel.cons@cern.ch> wrote:
> Hiram,
>
> We have to protect our brokers from misbehaving clients. The most
> simple case is a consumer that does not consume the messages in its
> queues (or durable subscriptions), wasting disk space, until it
> affects other clients (disk/partition full).
>
> Message expiration does help but only really works with constant
> message rates and sizes.
>
> It would be very good to have per-destinations quotas (at least using
> a message count but a total message size would be useful too) and have
> the broker deleting the oldest not yet consumed messages when needed.
> This way, the queues with quotas would become some kind of rings,
> using limited disk space.
>
> Do you think it's something Apollo could do?
>
> Cheers,
>
> Lionel
>