OVN.ovsdb_probe_interval takes effect only after initial database dump
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Terry Wilson |
Bug Description
ml2/ovn allows the configuration of the OVSDB session probe_interval, and defaults it to 60 seconds, overriding the python-ovs default of 5 seconds. It does this after the ovsdbapp Connection object is created and started, which means it is also after python-ovs sends a monitor request that pulls the initial copy of the database into memory. On a busy system with a large database, this can cause a failure since the 5 second default may not be sufficient to complete this request, causing a failure and infinite reconnection attempts with the error:
ERROR ovsdbapp.
3 years ago, functionality was added to python-ovs to pass the probe_interval value to the Idl so that it can be set immediately on the jsonrpc connection before connection, so we should use that.
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: ovn ovs |
Changed in neutron: | |
status: | In Progress → Fix Released |
Patch proposed by Terry: https:/ /review. opendev. org/c/openstack /neutron/ +/764235