On Wed, Jun 15, 2016 at 7:27 AM, Jeffrey Yunes <j...@yunes.us> wrote:
> Hi all, > After successful queries and a 10 minute wait, I'm getting the popular > "MySQL server has gone away." I have a single-threaded app and my > pool_recycle is way less than my wait_timeout. > > Do I need to create a new session after the pool recycles? I'd love to > know which part of the docs I've missed. > > I'm using oursql, so my problem sounds related to: > https://groups.google.com/forum/#!searchin/sqlalchemy/oursql$20gone$20away/sqlalchemy/K9Pk2pXbLgQ/XWzHnp5Ev4EJ > > Any suggestions? > > This might not have anything to do with your particular issue but I thought I'd share a particular instance we had the same things happening to us. And it turned out to have nothing to do with SQLAlchemy. We had an app running on Apache + mod_wsgi on a VM and the Web server and MySQL server were on the same VM. The VM didn't have much resources assigned to it. It turned out to be a disk IO on the VM host causing the MySQL to "go away". We have the same application running on AWS with hundreds of users and a shared MySQL backend and have had no issues. Once again; this might have nothing to do with your issue but just throwing it out there. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
