Ross Vandegrift wrote: > Hello everyone, > > I've got a particularly perplexing case of SQLAlchemy losing SQL > connections to a MySQL 4.1 database. > > Before you roll your eyes, I am familiar with both wait_timeout and > pool_recycle! > > > On the MySQL server, this is set to eight hours: > mysql> show variables like 'wait_timeout'; > +---------------+-------+ > | Variable_name | Value | > +---------------+-------+ > | wait_timeout | 28800 | > +---------------+-------+ > > In my production.ini on the web server, I have tried a few settings: > sqlalchemy.default.pool_recycle = 3600 > > and even: > sqlalchemy.default.pool_recycle = 600 > > Neither seems to help though. Anyone have any ideas? Perhaps I'm > doing something wrong in configuring production.ini?
MySQL can throw a 2013 and hang up if the resources needed by a SELECT exceed the server's configuration. I'd check the server logs for clues, then adjust the key_buffer, sort_buffer, etc. as required. The ORM can generate some pretty intense SQL with extreme ease. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
