Hi Ilya, I’m wondering whether there are possible configuration parameters for ovsdb relay -> main ovsdb server inactivity probe timer. My cluster experiencing issues where relay disconnects from main cluster due to 5 sec. inactivity probe timeout. Main cluster has quite big database and a bunch of daemons, which connects to it and it makes difficult to maintain connections in time.
For ovsdb relay as a remote I use in-db configuration (to provide inactivity probe and rbac configuration for ovn-controllers). For ovsdb-server, which serves SB, I just set --remote=pssl:<port>. I’d like to configure remote for ovsdb cluster via DB to set inactivity probe setting, but I’m not sure about the correct way for that. For now I see only two options: 1. Setup custom database scheme with connection table, serve it in same SB cluster and specify this connection when start ovsdb sb server. 2. Setup second connection in ovn sb database to be used for ovsdb cluster and deploy cluster separately from ovsdb relay, because they both start same connections and conflict on ports. (I don’t use docker here, so I need a separate server for that). Anyway, if I configure ovsdb remote for ovsdb cluster with specified inactivity probe (say, to 60k), I guess it’s still not enough to have ovsdb pings every 60 seconds. Inactivity probe must be the same from both ends - right? From the ovsdb relay process. I saw your talk on last ovscon about this topic, and the solution was in progress there. But maybe there were some changes from that time? I’m ready to test it if any. Or, maybe there’s any workaround? Regards, Vladislav Odintsov
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
