We should validate that the ovn-central ovsdb-server-election-timer is set to 4 or more.
1 second default does not allow for lag from any nova-compute ovsdb server or storage/network delays in heavily loaded production environments.
Some discussion in related bugzillas note that 4 seconds is the typical max most people have experienced needing to tune this to, but depending on deployments, we may want to err on the database being more stable in heavily loaded environments and set as high as 10 seconds. 10 minutes is the max setting.
Once this feature update is fix-released: https://bugs.launchpad.net/charm-ovn-central/+bug/1899371
We should validate that the ovn-central ovsdb-server-election-timer is set to 4 or more.
1 second default does not allow for lag from any nova-compute ovsdb server or storage/network delays in heavily loaded production environments.
Some discussion in related bugzillas note that 4 seconds is the typical max most people have experienced needing to tune this to, but depending on deployments, we may want to err on the database being more stable in heavily loaded environments and set as high as 10 seconds. 10 minutes is the max setting.
Imported from Launchpad using lp2gh.
date created: 2020-11-13T16:24:33Z
owner: afreiberger
assignee: aieri
the launchpad url