[rabbitmq-discuss] is anybody using 'immediate' publish?
randall at trellisapp.com
Fri Sep 14 13:34:01 BST 2012
Matthias / Simon, thanks for the background. I'm not using the immediate
flag, but I've considered using it.
Admittedly, I'm not fully aware of exactly how it works. It would be
helpful to have a better understanding of the semantics. Can you explain
what the publisher is notified of (if anything?) when there are 10 queues
bound to an exchange named HighPriority, a message with immediate flag true
is published to HighPriority, and 7 out of the 10 queues have the message
On Fri, Sep 14, 2012 at 8:03 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 14/09/12 12:53, Randall Richard wrote:
>> Just curious, are there any benefits for removing it -- is it preventing
>> / complicating support for other features?
> Well, the specific thing that we've bumped into in this case is that
> support for immediate is greatly slowing down HA queues. We could be
> smarter about this, at the cost of tangling the code further. So if we want
> to make HA queues faster (and we do!) we can either keep immediate and add
> a bunch of code at the same time, or remove immediate and delete a bunch of
> There are quite a number of places where we have notably greater
> complexity just to support this weird feature that (we suspect) no-one
> uses. It just feels very disproportionate.
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, VMware
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss