yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16781
[Bug 856764] Re: RabbitMQ connections lack heartbeat or TCP keepalives
** Also affects: fuel
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/856764
Title:
RabbitMQ connections lack heartbeat or TCP keepalives
Status in OpenStack Telemetry (Ceilometer):
In Progress
Status in Ceilometer icehouse series:
Fix Released
Status in Cinder:
New
Status in Fuel: OpenStack installer that works:
New
Status in Orchestration API (Heat):
Confirmed
Status in OpenStack Neutron (virtual network service):
In Progress
Status in OpenStack Compute (Nova):
Invalid
Status in Oslo - a Library of Common OpenStack Code:
In Progress
Status in Messaging API for OpenStack:
In Progress
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/ceilometer/+bug/856764/+subscriptions