yahoo-eng-team team mailing list archive

[OpenStack Infra <1930926@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/794892
Committed: https://opendev.org/openstack/neutron/commit/65cce351d74a9a637fdb2a9d5e0e63445dda9ea9
Submitter: "Zuul (22348)"
Branch:    master

commit 65cce351d74a9a637fdb2a9d5e0e63445dda9ea9
Author: Terry Wilson <twilson@xxxxxxxxxx>
Date:   Fri Jun 4 19:47:36 2021 +0000

    Use TCP keepalives for ovsdb connections
    
    When failing over OVN DB servers from one server to another, the
    server which originally hosted the VIP doesn't notice the connection
    is gone and doesn't reconnect. Ultimately, this is something that
    needs to be fixed in python-ovs, but setting the SO_KEEPALIVE socket
    option avoids the issue. This also has the benefit that the client
    doesn't need to send 'echo' requests, which can time out on an
    overloaded ovsdb-server, which causes a disconnection which then
    adds even more load on the ovsdb-server as it has to send the entire
    db contents over the wire after the connection.
    
    Closes-Bug: #1930926
    Change-Id: Ie0205785cab307c132fbe409588739685cade7c0


** 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/1930926

Title:
  Failing over OVN dbs can cause original controller to permanently lose
  connection

Status in neutron:
  Fix Released

Bug description:
  When failing over OVN DB servers from one server to another, the
  server which originally hosts the VIP doesn't notice the connection is
  gone and doesn't reconnect without restarting the neutron api service.

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