On Mon, 2021-03-01 at 17:02 +0100, Michal Arbet wrote: > Well, but that doesn't mean it's right that they don't have it configured. > If you google "net.ipv4.tcp_retries2 keepalive" and will read results, you > will see that this option is widely used this is something that operators can fix themselve externally however. im not against haveign kolla or other tools be able to configur it automticlly persay but its not kolla-ansibles job to configure every possible tuneing. this one might make sense to do by default or optionally but host config is largely out of scope of kolla ansible. in ooo where that is ment to handel all host config as well as openstack configuration or other tools where that is expliclty in socpe may also want to wtwee it but likely it shoudl be configurable. > > I think we have to discuss option value (not fix itself)...to find some > golden middle .. > > https://www.programmersought.com/article/724162740/ > https://knowledge.broadcom.com/external/article/142410/tuning-tcp-keepalive-for-inprogress-task.html > https://www.ibm.com/support/knowledgecenter/ko/SSEPGG_9.7.0/com.ibm.db2.luw.admin.ha.doc/doc/t0058764.html?view=embed > https://www.suse.com/support/kb/doc/?id=000019293 > https://programmer.group/kubeadm-build-highly-available-kubernetes-1.15.1.html > > po 1. 3. 2021 v 14:09 odesílatel Radosław Piliszek < > radoslaw.piliszek at gmail.com> napsal: > > > On Mon, Mar 1, 2021 at 11:06 AM Michal Arbet <michal.arbet at ultimum.io> > > wrote: > > > I really like the tool, thank you. also confirms my idea as this kernel > > option is also used by other projects where they explicitly mention case > > with keepalived/VIP switch. > > > > FWIW, I can see only StarlingX and Airship, none of general-purpose > > tools seem to mention customising this variable. > > > > -yoctozepto > >