[rabbitmq-discuss] Persistent messages and durable queue questions
fearsome.lucidity at gmail.com
Mon Jul 18 19:30:08 BST 2011
On Mon, Jul 18, 2011 at 10:02 AM, Matthias Radestock <matthias at rabbitmq.com>
> "absent" durable queues are only forgotten for routing purposes. RabbitMQ
> prevents re-creation of these queues since that would result in
> inconsistency when the node re-joins.
> We could change things s.t. absent durable queues still participate in
> routing and that confirms return a 'nack' when messages are routed to such
It seems like that is the correct thing to do.
> I am concerned though that there may be use cases where the current
> behaviour is the correct one.
I am curious as to what that case may be. A network partition in a cluster
like RabbitMQ's is an error condition. Thus, I expect the cluster to inform
me of the error, not to silently go on as if nothing is wrong.
AMQP is often compared with SMTP, with exchanges acting as MTAs and with
senders and receivers. A topic exchange is akin to a distribution list.
Publisher submit to the list and the message is sent to subscribers. If
there are no subscribers, then the publisher will receive no errors. But if
there are subscribers, but their mailbox is unreachable, then the subscriber
(or the MTA, depending on the configuration) will receive an error message.
At the moment RabbitMQ is failing to generate those error messages, so I
have no way of knowing whether the radio silence means there are no
subscribers or the subscriber failed to receive the message, actually is
worse, since I would actually get a publisher confirm ack, a positive
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss