[rabbitmq-discuss] RabbitMQ memory management
rabbitmq-discuss_efine at usa.net
Thu Sep 11 23:48:35 BST 2008
I don't know if I am reading this discussion correctly, but I am using
RabbitMQ specifically in a store-and-forward context. It should be able to
store persistent messages until the disk fills up even if no consumer is
draining the queue. If it is going to die because memory fills up before
forwarding gets done, that's a show-stopper for me. I don't mean to beat you
over the head by comparing RabbitMQ to WebSphere MQ, but it doesn't fall
over in this scenario unless the disk fills up (or the max queue depth is
reached), and even then, it just refuses to take more messages. IMHO, this
is how any messaging and queuing system that supports persistent messages
Please tell me I am misunderstanding.
On Thu, Sep 11, 2008 at 10:11 AM, Ben Hood <0x6e6562 at gmail.com> wrote:
> On Thu, Sep 11, 2008 at 2:34 PM, Eran Sandler <eran.sandler at gmail.com>
> > Just to be sure on the clustering side of things, when I cluster RabbitMQ
> > nodes they messages gets replicated to both servers, right?
> [This is now in the clustering section of the FAQs:
> Although we *could* do this, we don't, because it's too expensive.
> This would mean replicating every message across the the network in a
> synchronous fashion. And not too many *really* need it, in the event
> of a Rabbit node crashing, they just replay the log for that node.
> BBHoss started a discussion about this on IRC (look for the discusion
> about HA and DR between BBHoss and hal):
> Having said that, this may be a use case for pluggable queues, for the
> avail-o-nados out there :-)
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss