OVN.ovsdb_probe_interval takes effect only after initial database dump

Bug #1905611 reported by Terry Wilson
6
This bug affects 1 person
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.backend.ovs_idl.vlog [-] tcp:10.240.200.63:6642: no response to inactivity probe after 5.01 seconds, disconnecting"

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.

Tags: ovn ovs
Changed in neutron:
status: New → Confirmed
importance: Undecided → Medium
tags: added: ovn ovs
Revision history for this message
Slawek Kaplonski (slaweq) wrote :
Changed in neutron:
assignee: nobody → Terry Wilson (otherwiseguy)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 16.3.0

This issue was fixed in the openstack/neutron 16.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 17.1.0

This issue was fixed in the openstack/neutron 17.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 7.4.0

This issue was fixed in the openstack/networking-ovn 7.4.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 18.0.0.0rc1

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

Changed in neutron:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.