[rabbitmq-discuss] Troubleshooting handleCancel()

Srinath C srinath.c at gmail.com
Wed Apr 9 16:04:57 BST 2014

Hi MK,
    Thanks for your inputs. Below are my replies to your queries:
a, I can say for sure that there is part of this deployment which attempts
to explicit delete a queue or an exchange.
b, Queue master node failure could be a possibility. But I'm not sure if
the failed node was the master. How do you find it out by the way?
c, I have attached the rabbitmq logs for the surviving node. I have cropped
the logs to a few minutes before and after the handleCancel was called.
d, I can say for sure that publisher was connected to the surviving node.
The consumer - I believe was also connected to the surviving node because
of the fact that lyra would have otherwise recovered the queue and bindings.
e, Sure, will try out 3.3 to see if this issue occurs again.

Thanks again,

On Wed, Apr 9, 2014 at 1:31 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 9 April 2014 at 05:36:42, Srinath C (srinath.c at gmail.com) wrote:
> > > Scenario:
> > One of the rabbitmq nodes were brought down for testing.
> > It was observed that no more messages were being consumed
> Note that RabbitMQ 3.3.0 will automatically re-register consumers
> on a queue that had master failure. So I suggest giving your scenario
> a try with 3.3.
> --
> MK
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140409/ecae5855/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rabbitmq_survivor.log
Type: application/octet-stream
Size: 36663 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140409/ecae5855/attachment.obj>

More information about the rabbitmq-discuss mailing list