← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1513678] [NEW] At scale router scheduling takes a long time with DVR routers with multiple compute nodes hosting thousands of VMs

 

Public bug reported:

At scale when we have 100s of compute Node and 1000s of VM in networks that are routed by Distributed Virtual Router, we are seeing a control plane performance issue.
It takes a while for all the routers to be schedule in the Nodes.

The _schedule_router calls _get_candidates, and it internally calls
get_l3_agent_candidates. In the case of the DVR Routers, all the active
agents are passed to the get_l3_agent_candidates which iterates through
the agents and for each agent it tries to find out if there are any
dvr_service ports available in the routed subnet.

This might be taking lot more time.

So we need to figure out the issue and reduce the time taken for the
scheduling.

** Affects: neutron
     Importance: Undecided
     Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
         Status: In Progress


** Tags: l3-dvr-backlog

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

Title:
  At scale router scheduling takes a long time with DVR routers with
  multiple compute nodes hosting thousands of VMs

Status in neutron:
  In Progress

Bug description:
  At scale when we have 100s of compute Node and 1000s of VM in networks that are routed by Distributed Virtual Router, we are seeing a control plane performance issue.
  It takes a while for all the routers to be schedule in the Nodes.

  The _schedule_router calls _get_candidates, and it internally calls
  get_l3_agent_candidates. In the case of the DVR Routers, all the
  active agents are passed to the get_l3_agent_candidates which iterates
  through the agents and for each agent it tries to find out if there
  are any dvr_service ports available in the routed subnet.

  This might be taking lot more time.

  So we need to figure out the issue and reduce the time taken for the
  scheduling.

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


Follow ups