[ovirt-users] Timeout for Hosts

[Piotr Kliczewski]

I think that you are looking for vdsHeartbeatInSeconds which specifies
acceptable time of no activity.
You can increase it which would make it more resilient to network fluctuations.

Please note that it is part of the host life cycle and too big value
would limit our ability to detect real network issues.

Thanks,
Piotr

On Thu, Apr 27, 2017 at 8:36 AM, Oved Ourfali <oourfali at redhat.com> wrote:
> Hi Sven,
>
> Relevant configuration items are:
> vdsTimeout (which is set by default to 180 seconds, so you should be good)
> vdsHeartbeatInSeconds (this one should be increased)
>
> iirc no other changes are needed, but CC-ing Martin just in case i'm wrong.
>
> Best regards,
> Oved
>
> On Thu, Apr 27, 2017 at 9:30 AM, Sven Achtelik <Sven.Achtelik at eps.aero>
> wrote:
>>
>> Hi All,
>>
>>
>>
>> I have 2 hosts which are at remote locations where the ISP is forcing a
>> connection reset after some days. During that reset the connection will be
>> down for at most 2 minutes and the engine starts to complain about the hosts
>> not being reachable. What is the right value to tweak to compensate this ?
>>
>> Is it on of these: TimeoutToResetVdsInSeconds, VdsRefreshRate, vdsTimeout
>> ? And is it possible to only apply this for a certain cluster or DC or is it
>> global ?
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Sven
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>