Juan Hernandez has posted comments on this change. Change subject: core: Reduce host connection timeout ......................................................................
Patch Set 2: No, it wasn't tested in a WAN. However take into account that the 2 seconds time-out is just for the initial TCP handshake. To make this fail the network should have a one-way latency of approx 1 second, which is pretty bad even for a WAN and would make it probably unusable anyway. Also take into account that the fencing isn't triggered after one failed connection, but after at least 30 seconds of failed connections. In a previous comment I suggested adding a new vdcConnectionTimeout parameter so that we can make this configurable independently of the vdcTimeout. What default value would you suggest? -- To view, visit http://gerrit.ovirt.org/8410 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I55a49ae5d655c2105c5840decec81ae712e40c32 Gerrit-PatchSet: 2 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Juan Hernandez <juan.hernan...@redhat.com> Gerrit-Reviewer: Dan Kenigsberg <dan...@redhat.com> Gerrit-Reviewer: Doron Fediuck <dfedi...@redhat.com> Gerrit-Reviewer: Juan Hernandez <juan.hernan...@redhat.com> Gerrit-Reviewer: Laszlo Hornyak <lhorn...@redhat.com> Gerrit-Reviewer: Michael Kublin <mkub...@redhat.com> Gerrit-Reviewer: Yair Zaslavsky <yzasl...@redhat.com> Gerrit-Reviewer: Yaniv Kaul <yk...@redhat.com> _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
