Apparently dead connections can pile up in engine/agent rabbitmq

Bug #1460037 reported by Kirill Zaitsev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Won't Fix
High
Unassigned
Mitaka
Won't Fix
High
Unassigned
Newton
Confirmed
Undecided
Unassigned

Bug Description

Seems that engine can leave stale connections in rabbitmq, that are not dropped even if engine process/get's killed.

This can potentially lead to exhaustion of connections in rabbitmq, that would prevent new connections from being established and therefore deploys can hang during execution of agent.call/agent.prepare from muranopl.

The reason for this could be lack of timeout(kombu.Connection's, heartbeat parameter) during connection creation. Therefore connections in rabbitmq do not have a timeout and seem to stay there forever.
The issue can be mitigated by adding heartbeat parameter to murano.conf, that would control this option.

Changed in murano:
assignee: nobody → Kirill Zaitsev (kzaitsev)
Changed in murano:
importance: Undecided → High
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (master)

Fix proposed to branch: master
Review: https://review.openstack.org/187213

Changed in murano:
milestone: none → liberty-1
Changed in murano:
status: In Progress → Fix Released
Changed in murano:
status: Fix Released → In Progress
Changed in murano:
milestone: liberty-1 → liberty-2
Changed in murano:
milestone: liberty-2 → liberty-3
Changed in murano:
milestone: liberty-3 → liberty-rc1
Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

Preferred way to prevent this would be to use

[
 {rabbit, [{tcp_listen_options, [binary,
                                {packet, raw},
                                {reuseaddr, true},
                                {backlog, 128},
                                {nodelay, true},
                                {exit_on_close, false},
                                {keepalive, true}]}
          ]}
].

settings for rabbitmq.

no longer affects: murano/future
Changed in murano:
assignee: Kirill Zaitsev (kzaitsev) → nobody
status: In Progress → Won't Fix
no longer affects: murano/mitaka
no longer affects: murano/liberty
Changed in murano:
assignee: nobody → Kirill Zaitsev (kzaitsev)
milestone: liberty-rc1 → none
milestone: none → liberty-rc1
Changed in murano:
assignee: Kirill Zaitsev (kzaitsev) → nobody
Changed in murano:
milestone: mitaka-3 → mitaka-rc1
no longer affects: murano/liberty
no longer affects: murano/mitaka
no longer affects: murano/newton
Changed in murano:
status: Confirmed → Won't Fix
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on murano (master)

Change abandoned by Kirill Zaitsev (<email address hidden>) on branch: master
Review: https://review.openstack.org/187213

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.