yahoo-eng-team team mailing list archive

[ZongKai LI <lzklibj@xxxxxxxxxx>]

Public bug reported:

When dhcp-agent is restarted, it will restart all dhcp-drivers even no configurations or networks changed.
It's not a big deal in a small scale.
But in a big scale, like a dhcp-agent handles hundreds of networks, it will be quite a big cost to rebuild all these dhcp-drivers.

In our environment, a dhcp-agent which has more than 300 networks
binding onto it, will cost more than 2 mins to totally recover to work.
Indeed, nothing changed before we try to restart that dhcp-agent.

It's better to work in a "lazy" mode, like only restart dhcp-drivers
when their configure files need be changed.

** Affects: neutron
     Importance: Undecided
     Assignee: ZongKai LI (lzklibj)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => ZongKai LI (lzklibj)

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

Title:
  restart dhcp-agent shouldn't rebuild all dhcp-driver even nothing
  changed

Status in neutron:
  New

Bug description:
  When dhcp-agent is restarted, it will restart all dhcp-drivers even no configurations or networks changed.
  It's not a big deal in a small scale.
  But in a big scale, like a dhcp-agent handles hundreds of networks, it will be quite a big cost to rebuild all these dhcp-drivers.

  In our environment, a dhcp-agent which has more than 300 networks
  binding onto it, will cost more than 2 mins to totally recover to
  work. Indeed, nothing changed before we try to restart that dhcp-
  agent.

  It's better to work in a "lazy" mode, like only restart dhcp-drivers
  when their configure files need be changed.

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