[rabbitmq-discuss] RabbitMQ memory management
dmitriy.samovskiy at cohesiveft.com
Fri Sep 12 22:22:46 BST 2008
Ben Hood wrote:
> No, you've understood it correctly. If you send enough non-persistent
> messages, eventually the queues will fill up, the broker will crash
> and you will lose all of the messages that you sent to that node. ATM
I assume this condition can't happen by design if messages are published with immediate
flag set to true, right?
<field name = "immediate" type = "bit">
request immediate delivery
This flag tells the server how to react if the message cannot be
routed to a queue consumer immediately. If this flag is set, the
server will return an undeliverable message with a Return method.
If this flag is zero, the server will queue the message, but with
no guarantee that it will ever be consumed.
<doc name = "rule" test = "amq_basic_16">
The server SHOULD implement the immediate flag.
Does it mean a message is returned if it can't be immediately routed to a queue or a
message is returned if it can't be immediately routed to a consumer?
More information about the rabbitmq-discuss