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

[Laing, Michael P.]

Hi Tim,

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

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.

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.

Thanks,

Michael


On 5/13/13 6:50 AM, "Tim Watson" <tim at rabbitmq.com> wrote:

>Hi Michael,
>
>The sooner I can take a look at that config, the sooner I'll be able to
>verify what's going on and if necessary, get a fix ready for the patch
>release going out in the next week(s). One more question for you as well,
>if that's ok - are you running the shovel workers inside a cluster here?
>
>Cheers,
>Tim
>
>On 11 May 2013, at 16:43, Tim Watson wrote:
>
>> Sure that's fine, I'll look into it properly on Monday anyway.
>> 
>> Cheers,
>> Tim
>> 
>> On 11 May 2013, at 16:23, "Laing, Michael P."
>><Michael.Laing at nytimes.com> wrote:
>> 
>>> I'll get back to you as soon as I can but my human team is down for the
>>> weekend.
>>> 
>>> So there may be some delay.
>>> 
>>> Best,
>>> Michael
>>> 
>>> On 5/11/13 11:06 AM, "Tim Watson" <watson.timothy at gmail.com> wrote:
>>> 
>>>> 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.
>>>> 
>>>> Cheers,
>>>> Tim
>>>> 
>>>> On 11 May 2013, at 15:38, "Laing, Michael P."
>>>><Michael.Laing at nytimes.com>
>>>> wrote:
>>>> 
>>>>> correct
>>>>> 
>>>>> 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>
>>>>>> wrote:
>>>>>> 
>>>>>>> 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
>>>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>>> 
>>>>> _______________________________________________
>>>>> rabbitmq-discuss mailing list
>>>>> rabbitmq-discuss at lists.rabbitmq.com
>>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>> _______________________________________________
>>>> rabbitmq-discuss mailing list
>>>> rabbitmq-discuss at lists.rabbitmq.com
>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>> 
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>