Seems to be wokring. Thank you ! -----Ursprüngliche Nachricht----- Von: Piotr Kliczewski [mailto:[email protected]] Gesendet: Montag, 29. Mai 2017 10:41 An: Sven Achtelik <[email protected]> Cc: Oved Ourfali <[email protected]>; [email protected] Betreff: Re: [ovirt-users] Timeout for Hosts
Sven, This config value is hidden. You can update it by running: su - postgres -c "psql engine -c "UPDATE vdc_options set option_value = '<your value in seconds here>' where option_name = 'vdsHeartbeatInSeconds'"" Please note that the default value is 30 seconds. and next you need to restart your engine. Thanks, Piotr On Mon, May 29, 2017 at 10:30 AM, Sven Achtelik <[email protected]> wrote: > oVirt Engine Version: 4.1.2.2-1.el7.centos > > > -----Ursprüngliche Nachricht----- > Von: Piotr Kliczewski [mailto:[email protected]] > Gesendet: Montag, 29. Mai 2017 10:30 > An: Sven Achtelik <[email protected]> > Cc: Oved Ourfali <[email protected]>; [email protected] > Betreff: Re: [ovirt-users] Timeout for Hosts > > Sven, > > Which version of ovirt-engine do you use? > > Thanks, > Piotr > > On Mon, May 29, 2017 at 10:26 AM, Sven Achtelik <[email protected]> > wrote: >> Hi Piotr, >> >> I can't find that in the list of variables to set if I do an "engine-config >> -a" Is this something I have to setup first ? >> >> Thank you, >> Sven >> >> -----Ursprüngliche Nachricht----- >> Von: [email protected] [mailto:[email protected]] Im >> Auftrag von Sven Achtelik >> Gesendet: Donnerstag, 27. April 2017 10:04 >> An: Piotr Kliczewski <[email protected]>; Oved Ourfali >> <[email protected]> >> Cc: [email protected] >> Betreff: Re: [ovirt-users] Timeout for Hosts >> >> Ok, I'll try that one. >> >> Thank you >> >> -----Ursprüngliche Nachricht----- >> Von: Piotr Kliczewski [mailto:[email protected]] >> Gesendet: Donnerstag, 27. April 2017 09:59 >> An: Oved Ourfali <[email protected]> >> Cc: Sven Achtelik <[email protected]>; [email protected] >> Betreff: Re: [ovirt-users] Timeout for Hosts >> >> 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 <[email protected]> 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 >>> <[email protected]> >>> 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 >>>> [email protected] >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
