Bug 891420 - Change default for compute node to poll for database connection indefinitely
Summary: Change default for compute node to poll for database connection indefinitely
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: snapshot3
: 2.1
Assignee: Pádraig Brady
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-02 21:38 UTC by Perry Myers
Modified: 2022-07-09 06:09 UTC (History)
2 users (show)

Fixed In Version: openstack-nova-2012.2.3-1.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-21 18:14:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-16347 0 None None None 2022-07-09 06:09:14 UTC
Red Hat Product Errata RHSA-2013:0657 0 normal SHIPPED_LIVE Moderate: openstack-nova security, bug fix, and enhancement update 2013-03-21 22:12:14 UTC

Description Perry Myers 2013-01-02 21:38:04 UTC 
Description of problem:
Default behavior is for compute node to poll for connection to database 10 times before the service fails and dies

However in a production environment it is probably more useful to poll indefinitely, since it is possible a network disruption could last longer than 10 poll tries and you'd want the compute node to reconnect as soon as it can

So this bug is to change our default nova.conf file to contain:
sql_max_retries -1
Comment 1 Martin Magr 2013-01-15 15:31:00 UTC 
This setting could be done in spec file during installation.
Comment 2 Pádraig Brady 2013-01-28 17:10:11 UTC 
I need to think/test about the implications of this
Comment 7 Ami Jeain 2013-03-07 16:34:53 UTC 
verified in build openstack-nova-api-2012.2.3-4.el6ost.noarch using:
1. #service mysqld stop
2. watched the errors in the log files
3. restarted the mysqld service and made sure the reconnect occured
Comment 9 errata-xmlrpc 2013-03-21 18:14:42 UTC 
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-2013-0657.html
Note You need to log in before you can comment on or make changes to this bug.