[rabbitmq-discuss] Shovel stops receiving acks from cluster

Francesco Mazzoli francesco at rabbitmq.com
Wed Aug 15 14:32:09 BST 2012

At Wed, 15 Aug 2012 14:19:41 +0100,
Francesco Mazzoli wrote:
> At Tue, 14 Aug 2012 12:27:26 +0000,
> Jon Bergli Heier wrote:
> > I have a cluster consisting of two nodes, and brokers shoveling messages to
> > the cluster using the shovel plugin. When testing failover with the shovel
> > plugins (by stopping the RabbitMQ nodes) I often see that when starting a node
> > after stopping it causes the shovel plugin to stop receiving acks for
> > messages. I have prefetch_count set to 1000 in the shovel config, and I see
> > that "unacked" in the management interface for the queue rises to 1000 and
> > sits there, with "ready" steadily increasing.  The connection seems to be
> > alive as I can see (via tcpdump) that there are heartbeats being sent.  All
> > RabbitMQ servers are 2.8.5 on Erlang R14A. This only seems to happen with
> > setting ack_mode set to on_confirm. The queues on the cluster are mirrored
> > using x-ha-policy: all.
> Could you post more details about your shovel config and your HA cluster?  In
> particular, how do you handle failover?  Do you have the cluster nodes all as
> sources in the shovel config?

Also, you might want to check the shovel status,

Francesco * Often in error, never in doubt

More information about the rabbitmq-discuss mailing list