[rabbitmq-discuss] Persister crashes Rabbit
rrabarg2 at yahoo.com.sg
Sat Nov 15 21:47:36 GMT 2008
We have a system which includes a homogeneous set of message producers
(we call switches) and a backoffice application which consumes these
messages. We have a guaranteed delivery requirement for the messages,
we also require that the switches can continue to operate unhindered
(assuming infinite disk space) during long periods of slow or
non-consumption of messages by the backoffice. I'm not familiar with
rabbitMQ, but the implication I take from this thread is that rabbitMQ
would not meet our requirements (at least not without significant extra
bespoke work) - is that a fair statement?
Ben Hood wrote:
> On Sat, Nov 15, 2008 at 6:43 PM, Ilya Grigorik <ilya at aiderss.com> wrote:
>> - If we connect multiple nodes together (without persistence), and then
>> create an exchange, the in-memory queues will be replicated across all
> No, only broker entities are replicated (exchanges, queues and
> bindings), but not the actual messages as indicated in the clustering
> guide: http://www.rabbitmq.com/clustering.html
> The reason for this is primarily the cost of inter-node message replication.
>> - Assuming the cluster is running, is it up to the client to determine which
>> node it wants to connect to (either explicitly, or through some load
>> balancer in between)?
>> - Now, if we add persistence to the queue, will a copy of the queue be
>> stored on each node in the cluster?
> You a queue only exists on one node in the cluster. Persistent
> messages that are routed to a queue are written to disk on the node
> where the queue exists. Also you need to differentiate between
> persistent messages (a property that the publisher sets) and
> persistent queue (a property that is set when creating a queue). The
> implication is that you can send persistent messages to a transient
> queue and vice versa.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss