[rabbitmq-discuss] Shovel 3.1.0 - terminates on unknown_host error instead of seeking another host
watson.timothy at gmail.com
Sat May 11 16:06:33 BST 2013
Right, well that's another matter altogether. Once a reconnect delay is properly set, the worker should keep trying to restart (and in the process, choose a different random URL). Can you confirm how/where you set the reconnect delay please, and also what your shovel config looks like once all the substitution is done - you can replace all the IP digits with x using sed or somesuch.
This is top of my personal list to fix for 3.1.1 right now.
On 11 May 2013, at 15:38, "Laing, Michael P." <Michael.Laing at nytimes.com> wrote:
> On 5/11/13 10:35 AM, "Tim Watson" <watson.timothy at gmail.com> wrote:
>> Hi Michael,
>> On 11 May 2013, at 12:41, "Laing, Michael P." <Michael.Laing at nytimes.com>
>>> That temporary fix does not work. This is a different bug.
>>> With the 'fix' it gives a bad_host error instead of unknown_host.
>> You're saying that the error changes *and* the shovel worker terminates
>> without trying to reconnect to another host?
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss