#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout
passed
-------------------------------------+-------------------------------------
Reporter: ekeydar@… | Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) | Resolution: wontfix
Severity: Release blocker | Triage Stage: Accepted
Keywords: mysql | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jeroen.pulles@…):
My preferred solution is to increase the wait_timeout to 86400 (24hr) on
sessions from processes that are long lived. Otherwise I have to do a
close before any blocking call to other systems, e.g. redis, which may
block for a month or return in a split second. These blocking calls are
mostly in loops; Under load they are repeatedly called. I am not about to
add a connection.close() call in those code paths. (And this is where the
MySQL reconnect behavior worked fine, it only kicked in whén there was a
timeout).
http://dev.mysql.com/doc/refman/5.6/en/auto-reconnect.html
--
Ticket URL: <https://code.djangoproject.com/ticket/21597#comment:31>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/075.11646fa3cd1235705bfe6746afa72e30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
