[rabbitmq-discuss] Shovel 3.1.0 - terminates on unknown_host error instead of seeking another host
Laing, Michael P.
Michael.Laing at nytimes.com
Fri May 10 13:29:02 BST 2013
With 3.1.0 our shovel configurations, which worked well in 3.0.4 and prior, now fail due to unknown_host errors.
In these configurations, we put all possible hostnames (usually 6) in the sources / destinations lists. We do this as a convenience because we have automated deployments in AWS EC2 and we don't know ahead of time how many zones in a region will have instances nor exactly which zones – but we can preallocate ip addresses in the VPC and set up a standard /etc/hosts file with all possible hosts. However there may not actually be an instance running at each IP.
Previously the shovel would always find one of the actual instances, or remain in the 'starting' state.
Now the shovel terminates if a host is not found.
We can smarten up our configuration but that doesn't address the real problem: if a host has failed, we want the shovel to always seek another host and not terminate.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss