pool recycle means a connnection that is 3600 seconds old will be thrown away. does not help with reconnects.
When a "server gone away" error is detected, the entire connection pool is thrown away and rebuilt. So assuming one engine, you'd get this error once for each connection that is still checked out and attempts a new operation. Subsequent transactions will proceed since the pool has been rebuilt. There was also a Mysql-reconnect bug fixed in 0.6.3 where previous versions might have impacted this. On Oct 23, 2010, at 3:31 AM, Chris Withers wrote: > Hi Guys, > > One of our MySQL servers crashed yesterday. After we recovered it, a small > SQLAlchemy-based app we have running against it kept throwing 'MySQL server > has gone away' even though we have pool_recycle set to 3600. > > Any ideas why that might be? > Curious as to why SA doesn't try and reconnect when it gets this exception? > > cheers, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
