On Tue, Jun 08, 2021 at 10:27:08AM +0100, [email protected] wrote: > From: Anton Ivanov <[email protected]> > > Set a soft time limit of "raft election timer"/2 on ovsdb > processing. > > This improves behaviour in large heavily loaded clusters. > While it cannot fully eliminate spurious raft elections > under heavy load, it significantly decreases their number. > > TODO: randomize session processing order to ensure individual > sessions towards the end of the remotes list are not starved > > Signed-off-by: Anton Ivanov <[email protected]>
Personally I'd consider a random or round-robin processing order to be pretty critical here. A better approach (which would be a lot more work) would be for the Raft code to use a separate thread or process. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
