yahoo-eng-team team mailing list archive

[Ed Bak <ed.bak2@xxxxxx>]

Public bug reported:

With dvr enabled , neutron remove-router-interface significantly
degrades in response time as the number of l3_agents and the number of
routers increases.   A significant contributor to the poor performance
is due to check_ports_exist_on_l3agent.  The call to
get_subnet_ids_on_router returns an empty list since the port has
already been deleted by this point.  The empty subnet list is then used
as a filter to the subsequent call core_plugin.get_ports which
unexpectedly returns all ports instead of an empty list of ports.
Erroneously looping through the entire list of ports is the biggest
contributor to the poor scalability.

** Affects: neutron
     Importance: Undecided
     Assignee: Ed Bak (ed-bak2)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Ed Bak (ed-bak2)

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

Title:
  remove_router_interface doesn't scale well with dvr routers

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  With dvr enabled , neutron remove-router-interface significantly
  degrades in response time as the number of l3_agents and the number of
  routers increases.   A significant contributor to the poor performance
  is due to check_ports_exist_on_l3agent.  The call to
  get_subnet_ids_on_router returns an empty list since the port has
  already been deleted by this point.  The empty subnet list is then
  used as a filter to the subsequent call core_plugin.get_ports which
  unexpectedly returns all ports instead of an empty list of ports.
  Erroneously looping through the entire list of ports is the biggest
  contributor to the poor scalability.

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