Re: [Openstack] MySQL connection gone away handling in OpenStack projects

[Adam Gandelman]

On 03/22/2012 09:48 AM, Vishvananda Ishaya wrote:
This looks like a much better solution than MySQLPingListener.  It 
would be good to get this into common / nova, especially if we can 
verify that it works with postgres as well.


Vish


+1 for making this the standard method of initializing databases across 
projects.  A quick test of adding a wrapped call to _ENGINE.connect() in 
the main try/except block of configure_db seems to totally solve the 
issue of services starting at boot before a database is reachable, 
reported @ https://bugs.launchpad.net/ubuntu/+source/nova/+bug/959426


-Adam
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] MySQL connection gone away handling in OpenStack projects

[Vishvananda Ishaya]

This looks like a much better solution than MySQLPingListener.  It would be 
good to get this into common / nova, especially if we can verify that it works 
with postgres as well.

Vish

On Mar 22, 2012, at 7:48 AM, Unmesh Gurjar wrote:

 Hi,
  
 The current handling of the ‘SQL server has gone away’ is different across 
 OpenStack projects (eg. Nova uses MySQLPingListener, whereas Glance retries 
 the db operation to recover connection).
 I am curious to know if the fix implemented in 
 https://review.openstack.org/5552 will be used across all projects (through 
 openstack-common) ?
  
 Thanks  Regards,
 Unmesh G.
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp