Juan Hernandez has posted comments on this change. Change subject: core: Make connection timeout configurable ......................................................................
Patch Set 10: Verified Rebased and made the new configuration parameters "general" instead of version specific. The default values are such that the behavior will be exactly the same that now. In order to verify I changed the parameters as follows: engine-config -s vdsConnectionTimeout=2 engine-config -s vdsRetries=1 service ovirt-engine restart Then in the host I added the following iptables rule to drop requests to VDSM and thus simulate a complete loss of connectivity: iptables --table filter --insert INPUT --protocol tcp --dport 54321 --jump DROP With that the initial fencing attempt happens after 60 seconds, as defined in the TimeoutToResetVdsInSeconds parameter. -- 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: 10 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Juan Hernandez <[email protected]> Gerrit-Reviewer: Dan Kenigsberg <[email protected]> Gerrit-Reviewer: Doron Fediuck <[email protected]> Gerrit-Reviewer: Juan Hernandez <[email protected]> Gerrit-Reviewer: Laszlo Hornyak <[email protected]> Gerrit-Reviewer: Michael Kublin <[email protected]> Gerrit-Reviewer: Noam Slomianko <[email protected]> Gerrit-Reviewer: Omer Frenkel <[email protected]> Gerrit-Reviewer: Yair Zaslavsky <[email protected]> Gerrit-Reviewer: Yaniv Kaul <[email protected]> _______________________________________________ Engine-patches mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-patches
