Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1060772 - nova qpid reconnection delay must be more accurate
nova qpid reconnection delay must be more accurate
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
4.0
Unspecified Unspecified
urgent Severity urgent
: z4
: 4.0
Assigned To: Flavio Percoco
Toure Dunnon
: Rebase, Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-03 09:53 EST by Fabio Massimo Di Nitto
Modified: 2016-04-26 09:25 EDT (History)
11 users (show)

See Also:
Fixed In Version: openstack-nova-2013.2.3-1.el6ost
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Qpid's driver reconnection delay is not configurable. This and the fact that the hard-coded delay was quite high became a blocker issue from an HA perspective. Making this value configurable is not possible for this version, hence the hard-coded delay was tweaked and made reasonable HA-wise. The new delay cap is 5 seconds.
Story Points: ---
Clone Of: 1060689
Environment:
Last Closed: 2014-05-29 16:35:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1281148 None None None Never
OpenStack gerrit 83689 None None None Never
Red Hat Product Errata RHSA-2014:0578 normal SHIPPED_LIVE Moderate: openstack-nova security, bug fix, and enhancement update 2014-05-29 20:27:05 EDT

  None (edit)
Description Fabio Massimo Di Nitto 2014-02-03 09:53:07 EST
+++ This bug was initially created as a clone of Bug #1060689 +++

The current loop is:

        delay = 1
        while True:
            # Close the session if necessary
            if self.connection.opened():
                try:
                    self.connection.close()
                except qpid_exceptions.ConnectionError:
                    pass

            broker = self.brokers[attempt % len(self.brokers)]
            attempt += 1

            try:
                self.connection_create(broker)
                self.connection.open()
            except qpid_exceptions.ConnectionError, e:
                msg_dict = dict(e=e, delay=delay)
                msg = _("Unable to connect to AMQP server: %(e)s. "
                        "Sleeping %(delay)s seconds") % msg_dict
                LOG.error(msg)
                time.sleep(delay)
                delay = min(2 * delay, 60)

that can lead to over 60 seconds waiting time if the qpid sever is not immediately available at startup.

60 seconds is too long for HA environment where timers need to be very aggressive to reduce downtime to the very minimum.

This is a blocker for HA deployments.
Comment 9 errata-xmlrpc 2014-05-29 16:35:07 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0578.html

Note You need to log in before you can comment on or make changes to this bug.