yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

Public bug reported:

It has been revealed that under load (when a bunch of networks is
processed) DHCP agent fails to send heartbeat updates and neutron-server
starts to consider it dead.

In network failover feature this has been worked around by checking if
DHCP agent has just started up and giving it amount of time proportional
to number of networks scheduled to it.

However in scheduling logic there's no such additional liveliness
conditions, so starting agent may be considered dead and network will be
scheduled on additional agent beyond configured limit.

So in order to avoid such negative side effect, agent liveliness check
logic needs to be unified.

** Affects: neutron
     Importance: Medium
     Assignee: Eugene Nikanorov (enikanorov)
         Status: New


** Tags: l3-ipam-dhcp

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

Title:
  Improve logic that determines liveliness of dhcp agent

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  It has been revealed that under load (when a bunch of networks is
  processed) DHCP agent fails to send heartbeat updates and neutron-
  server starts to consider it dead.

  In network failover feature this has been worked around by checking if
  DHCP agent has just started up and giving it amount of time
  proportional to number of networks scheduled to it.

  However in scheduling logic there's no such additional liveliness
  conditions, so starting agent may be considered dead and network will
  be scheduled on additional agent beyond configured limit.

  So in order to avoid such negative side effect, agent liveliness check
  logic needs to be unified.

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