openstack team mailing list archive

Thread
Date

Using durable queues

To: "openstack@xxxxxxxxxxxxxxxxxxx (openstack@xxxxxxxxxxxxxxxxxxx) (openstack@xxxxxxxxxxxxxxxxxxx)" <openstack@xxxxxxxxxxxxxxxxxxx>
From: "Day, Phil" <philip.day@xxxxxx>
Date: Mon, 28 Jan 2013 14:00:00 +0000
Accept-language: en-GB, en-US
Thread-index: Ac39Xmf2JAOJz51xQUWS0idCsxFkBQ==
Thread-topic: Using durable queues

Hi Folks,

I'm trying to understand the configuration required to create a durable notification queue for billing with RabbitMQ.   As I understand it for messages to be durable there need to be three things:

-          The exchange has to be created as durable

-          The queue needs to be created as durable

-          Messages themselves need to be marked as durable when they are published.

I can see that setting rabbit_durable_queues=True would create the exchange and notification publisher with the options required for me to create a durable queue for a billing system, but I thought there was a concern in having durable queues in general within Nova because if the consumer fails and recovers it may receive the same message multiple times  - so is there some magic in the system which prevents all of the other topic queues from becoming durable when this option is set (or is there no problem with durable queues in general) ?

Cheers,
Phil