On 7/12/24 08:11, Vladislav Odintsov wrote: > Hi Krzysztof, > > talking about OVN < 23.09: > > 1. For the main OF connection which is used to configure OF flows, the > probing is disabled by default. Just ensure that > external_ids:ovn-openflow-probe-interval is not configured. The disconnects > are harmful for ha-chassis-group functioning (false-positive failover > events), which lead to flows recomputing and traffic interruptions. > 2. There are still two OF connections for packet-ins and feature probing, > which have hardcoded enabled probing with constant interval of 5 seconds. > Disconnects on them are not harmful (just waist CPU time on connection > re-instantiation). > > For all OVN versions: the mentioned patch and settings disable probing only > in OVN -> OVS direction. The reverse direction still uses default probing > configured from OVS side. OVN doesn’t configure OVS OF probing yet, so you > should consider it on your own. For more details see thread [1]. > > So, I guess the backport is possible but not very necessary (if you have > another inputs, please provide). > > The discussion about default OVS bridge probe configuration stopped here [2], > but we can continue from that point. > > @Ilya, what do you think about disabling OF probes by default for unix domain > sockets in OVS? If you’re okay with it, I can work on it and submit a patch.
I think, the conclusion of previous discussions was that the probe should stay because it is part of the OpenFlow standard, but it should be configurable, so users can disable it, if they want to, which is also part of the OpenFlow standard. (I believe this was discussed somewhere on the other thread, but I can't find it...) One way to do that is to create the controller record for the main management controller in the database from ovs-vswitchd, if it doesn't already exist, so users can change the values in the database record, if they need to. Best regards, Ilya Maximets. > > 1: https://mail.openvswitch.org/pipermail/ovs-dev/2023-June/405296.html > 2: https://mail.openvswitch.org/pipermail/ovs-dev/2023-September/408070.html > > regards, > Vladislav Odintsov > >> On 11 Jul 2024, at 17:41, Krzysztof Tomaszewski via discuss >> <ovs-discuss@openvswitch.org> wrote: >> >> >> Hello, >> >> In newer release of OVN there is already disabled OpenFlow inactivity probing >> (disscussion [1], commit [2]) but problem still exist in v22.03. >> >> IMHO problem is quite impacting as it causes many reconnections after 5s of >> inactivity >> even on medium scale deployments which leads to OVN system instability. >> >> Worth to mention is that v22.03 release is still main OVN package version in >> many LTS distributions >> like Ubuntu 22.04. >> >> Are there any plans to include those changes (disable inactivity probing for >> OpenFlow) in OVN v22.03 release? >> >> >> 1: https://mail.openvswitch.org/pipermail/ovs-dev/2023-May/404625.html >> 2: >> https://github.com/ovn-org/ovn/commit/c16e5da803838fa66129eb61d7930fc84d237f85 >> >> Regards, >> >> Krzysztof Tomaszewski >> _______________________________________________ >> discuss mailing list >> disc...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
