[rabbitmq-discuss] Shovels not reconnecting with RabbitMQ 3.1.0

Tim Watson tim at rabbitmq.com
Thu May 2 14:56:02 BST 2013

On 2 May 2013, at 11:29, Jon Bergli Heier wrote:

> Hello, after upgrading to RabbitMQ 3.1.0 my shovels doesn't seem to reconnect automatically. I don't have reconnect_delay set, so I'm assuming they should use the default, which is 5 seconds according to the shovel docs (http://www.rabbitmq.com/shovel.html).

I've just checked and the default reconnect delay is still set to 5 seconds.

> The shovels are on non-clustered brokers, connecting to a two-node cluster.

Hmn. If the shovels were clustered then it's possible a named shovel's configuration from one node could override the other (due to the way in which individual shovel workers fail-over in 3.1), but you say they're not clustered. Hmn. I'll have a quick go at reproducing this, but AFAICT there's no reason they shouldn't be attempting to reconnect. Unless the reconnect_delay is being overridden somewhere?


More information about the rabbitmq-discuss mailing list