#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 pembo13):
Could someone give a little more context to this issue? I ran into it the
very first morning after upgrading from 1.5.x to 1.6.x, I am guessing
because the app saw no use for a few hours (2am to 8am). I had
'CONN_MAX_AGE' set to 15mins, but have had wait_timeout and
interactive_timeout set to 5mins.
So in my case, I don't exactly know my program is going to be idle for a
long time, though my wait_timeout didn't seem that low. I've preemptively
adjusted my wait_timeout to 30mins and my interactive_timeout to 60mins,
but a bit more explanation of the issue. I don't yet see the relation to
#15119.
Also, this issue should probably be mentioned in the docs somewhere.
--
Ticket URL: <https://code.djangoproject.com/ticket/21597#comment:30>
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.80af482eee465a79f1f4f28e9c08047f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
