#10402: mysql backend connections left idle open
-------------------------------------+-------------------------------------
Reporter: DirkDatzert | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.4
(models, ORM) | Resolution: needsinfo
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => needsinfo
Comment:
I'm fairly sure that this is related to your particular setup and not
anything specific in Django. For example, if you've got code that connects
to the database in your uwsgi config before uwsgi forks, that'll leak
database connections. There isn't a ton that we can do about that; those
connections get created "outside" Django essentially. In our
experimentation, we couldn't make this happen unless we did something
along those lines. So I think this is a problem with your configuration,
not with Django itself.
It's possible I'm wrong, and if you do think this is a Django bug and can
provide more information to help us reproduce it please feel free to
reopen. But we're going to need a fair bit of information -- ideally a
very small app that easily recreates the issue. And please do try to
reproduce against Django master; connection handling's completely changed,
and we won't be making any further improvements to the version shipping in
1.5.
--
Ticket URL: <https://code.djangoproject.com/ticket/10402#comment:9>
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].
For more options, visit https://groups.google.com/groups/opt_out.
