OpenStack Compute (nova)

impl_qpid reconnects in a busy loop

Bug #929784 reported by Russell Bryant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Russell Bryant
OpenStack Compute (nova) 2012.1 "essex"

Bug Description

Qpid has automatic reconnect handling. The current code in impl_qpid makes it so this code attempts to reconnect in a busy loop. The default behavior should be more sane than that. Patch coming shortly.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/3976
Committed: http://github.com/openstack/nova/commit/b12c20fc48d82a6b888dee761dd46959d21d556a
Submitter: Jenkins
Branch: master

commit b12c20fc48d82a6b888dee761dd46959d21d556a
Author: Russell Bryant <email address hidden>
Date: Thu Feb 9 15:07:51 2012 -0500

    Don't tell Qpid to reconnect in a busy loop.

    Fix bug 929784.

    Don't set any of the reconnect timing options unless they have been set
    in the configuration. Setting them all to zero puts Qpid in a mode
    where it will reconnect in a busy loop. By not setting these unless a
    non-zero value has been provided, Qpid goes back to its default
    behavior, which is to use an exponential backoff on reconnect attempts
    (after 1 second, then 2, 4, 8, etc).

    Change-Id: Ia587bbe96db9ea6e429af289c3d586f4c6706648

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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