[rabbitmq-discuss] BUG: Failing nodes with HA-queue stops message flow

Matthias Radestock matthias at rabbitmq.com
Mon Oct 1 15:22:57 BST 2012


On 01/10/12 15:07, Simon Lundström wrote:
> I have no idea how *I* should be handling consumer cancel notification
> (can't find this in the documentation), but I'm pretty sure Ruby AMQP
> handles it, see
> <https://github.com/ruby-amqp/amq-client/commit/49951878a8ff4bdbcead3c13eb7737ade6e70669>
> and <https://groups.google.com/forum/#!topic/ruby-amqp/KKxv4DFVJVk>.

It *supports* CCNs, but I am pretty sure you'll need to set up a call 
back to actually *handle* them (i.e. re-consume).

> How can I see the client properties (to check if my consumer reports
> support for CCN) in the management GUI?

They should be shown on the connection details page.

> Under Connections => Consumer IP, Client properties I only get:
> information http://github.com/ruby-amqp/amqp
> platform  ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin11.0]
> version 0.9.7
> product AMQP gem

I suspect your version of the gem is too old.

> I'll ask on their mailinglist.

Good idea.

> Aaah, and the reason for this not happening when disk01 is master and
> then restarted is because the consumer is connected to disk01 and must
> reconnect (because it just lost the connection)?


> Oh, why mailed here in the first place was becuase Emile thought it was
> strange that ram01 threw this message:
> =ERROR REPORT==== 1-Oct-2012::13:55:35 ===
> Discarding message {'$gen_call',{<0.173.0>,#Ref<>},{notify_down,<6733.320.0>}} from <0.173.0> to <0.200.0> in an old incarnation (1) of this node (2)

I don't think that indicates a problem.

> But maybe that's when the consumer doesn't handle basic.cancel?

Nah, definitely unrelated to that.



More information about the rabbitmq-discuss mailing list