[rabbitmq-discuss] Shovel 3.1.0 - terminates on unknown_host error instead of seeking another host

Tim Watson tim at rabbitmq.com
Mon May 13 13:53:54 BST 2013

On 13 May 2013, at 12:23, Laing, Michael P. wrote:

> Hi Tim,
> The guy who did the test won't be available for 3-4 hours yet.

Ok, no rush. I'm on leave Tue+Wed, but I can look at this later on tonight if needs be. I'd like to get to the bottom of it.

> And - I couldn't recreate his results manuallyŠ! I.e., setting
> reconnect_delay worked for me.
> So this may not be a new bug.
> But I want to talk to him first before we close it out and see if he did
> something subtly different.

That sounds sensible.

> Re cluster: the 5 shovels are configured and running in a non-clustered
> node. The remote party is a cluster of 1 to 3 nodes with each remote node
> reachable via one of 6 hostnames defined in each shovel.

Ok fine, that rules out some of the explanations I might've had, but it's good we eliminate possibilities.


More information about the rabbitmq-discuss mailing list