yahoo-eng-team team mailing list archive

[Brian Haley <1905611@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1905611

Title:
  OVN.ovsdb_probe_interval takes effect only after initial database dump

Status in neutron:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1905611/+subscriptions