← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1958593] [NEW] [ovn]neutron-server allow more efficient reconnections when connecting to clustered OVSDB servers.

 

Public bug reported:

When our cluster has a lot of data, once theNB/SB needs to be
reconnected (the NB/SB is disconnected or the leader switches), neutron
needs to resynchronize and process all the data from NB/SB, which will
occupy resources. Moreover, creating a virtual machine during
reconnection may cause a timeout waiting for network-vif-plugged.

python-ovs support for monitor_cond_since / update3 to allow more efficient reconnections when connecting to clustered
OVSDB servers[1].

neutron-server only uses python-ovs. it should not be care whether it is
fast synchronization or full synchronization. It only needs to update
python-ovs to achieve fast synchronization.

But neutron-sever monitors the database schema changes[2]. each
reconnection triggers a create database event, call updaet_tables, and
clear cache. this means that fast synchronization cannot be used.

can we not support updated or downgraded(now it only for Table
'Chassis_Private') while neutron-server is running?


[1] https://github.com/openvswitch/ovs/commit/46d44cf3be0dbf4a44cebea3b279b3d16a326796
[2] https://review.opendev.org/c/openstack/neutron/+/760967

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  [ovn]neutron-server allow more efficient reconnections when connecting
  to clustered OVSDB servers.

Status in neutron:
  New

Bug description:
  When our cluster has a lot of data, once theNB/SB needs to be
  reconnected (the NB/SB is disconnected or the leader switches),
  neutron needs to resynchronize and process all the data from NB/SB,
  which will occupy resources. Moreover, creating a virtual machine
  during reconnection may cause a timeout waiting for network-vif-
  plugged.

  python-ovs support for monitor_cond_since / update3 to allow more efficient reconnections when connecting to clustered
  OVSDB servers[1].

  neutron-server only uses python-ovs. it should not be care whether it
  is fast synchronization or full synchronization. It only needs to
  update python-ovs to achieve fast synchronization.

  But neutron-sever monitors the database schema changes[2]. each
  reconnection triggers a create database event, call updaet_tables, and
  clear cache. this means that fast synchronization cannot be used.

  can we not support updated or downgraded(now it only for Table
  'Chassis_Private') while neutron-server is running?

  
  [1] https://github.com/openvswitch/ovs/commit/46d44cf3be0dbf4a44cebea3b279b3d16a326796
  [2] https://review.opendev.org/c/openstack/neutron/+/760967

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