← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1433940] [NEW] dhcp-agent: too many pending messages for inactive node

 

Public bug reported:

Neutron server keeps sending notification messages (e.g. port
create/update/delete, network create/update/delete etc. ) to all dhcp-
agents including inactive ones. This creates a problem that after
running for a long time there can be huge amount of pending messages in
rabbitmq for those inactive nodes.

The consequence is, when those inactive nodes are back to active, it
will stuck if there are too many messages to handle (depends on how long
the agent has stayed in inactive state), and sometime failed to start
properly due to errors like:

ERROR neutron.openstack.common.rpc.common [-] Failed to consume message
from queue: [Errno 104] Connection reset by peer

So the proposal is to send notifications to active nodes only.

** Affects: neutron
     Importance: Undecided
         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/1433940

Title:
  dhcp-agent: too many pending messages for inactive node

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Neutron server keeps sending notification messages (e.g. port
  create/update/delete, network create/update/delete etc. ) to all dhcp-
  agents including inactive ones. This creates a problem that after
  running for a long time there can be huge amount of pending messages
  in rabbitmq for those inactive nodes.

  The consequence is, when those inactive nodes are back to active, it
  will stuck if there are too many messages to handle (depends on how
  long the agent has stayed in inactive state), and sometime failed to
  start properly due to errors like:

  ERROR neutron.openstack.common.rpc.common [-] Failed to consume
  message from queue: [Errno 104] Connection reset by peer

  So the proposal is to send notifications to active nodes only.

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


Follow ups

References