Had a node crash in a cluster (due to memory exhaustion). When clients then
reconnected to a healthy node, bind commands failed to return. And when the
crashed node was restarted the logs was flooded with:


=ERROR REPORT==== 5-Aug-2013::23:45:50 ===
Discarding message
{'$gen_call',{<0.7975.0>,#Ref<0.0.0.244595>},{deliver,{delivery,true,<5068.31152.5031>,{basic_message,{resource,<<8
bytes>>,exchange,<<16 bytes>>},[<<7 bytes>>],{content,60,{'P_basic',<<24
bytes>>,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined},<<27
bytes>>,rabbit_framing_amqp_0_9_1,[<<299 bytes>>]},<<16
bytes>>,false},396},true}} from <0.7975.0> to <0.26389.5794> in an old
incarnation (3) of this node (1)


The only solution was to restart all nodes in the cluster.








--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Node-crash-tp28595.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 4 | next ›
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedAug 6, '13 at 7:15a
activeAug 6, '13 at 11:00a
posts4
users3
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2017 Grokbase