yahoo-eng-team team mailing list archive

[Justin Hopper <justin.hopper@xxxxxx>]

The version of kombu we are now using and the py-amqp lib that provides
the transport supports heartbeat.

Heartbeat will help close connections when a client using rabbit is
forcefully terminated.

Using heartbeats may be an option and if so can either be exposed to the
rpc-component user by way of server-params or a configuration for the
rpc-component.

** Also affects: oslo
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: Invalid => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/856764

Title:
  RabbitMQ connections lack heartbeat or TCP keepalives

Status in OpenStack Compute (Nova):
  New
Status in Oslo - a Library of Common OpenStack Code:
  New

Bug description:
  There is currently no method built into Nova to keep connections from
  various components into RabbitMQ alive.  As a result, placing a
  stateful firewall (such as a Cisco ASA) between the connection
  can/does result in idle connections being terminated without either
  endpoint being aware.

  This issue can be mitigated a few different ways:

  1. Connections to RabbitMQ set socket options to enable TCP
  keepalives.

  2. Rabbit has heartbeat functionality.  If the client requests
  heartbeats on connection, rabbit server will regularly send messages
  to each connections with the expectation of a response.

  3. Other?

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