Opened 5 years ago
Last modified 5 years ago
#31373 closed Bug
Django 3.x / uwsgi is leaking connections — at Initial Version
Reported by: | Marcin Nowak | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 3.0 |
Severity: | Release blocker | Keywords: | |
Cc: | Andrew Godwin, Simon Charette | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Project upgraded from 2.x to 3.0.4 is leaking PostgreSQL database connections.
ATOMIC_REQUESTS=False, AUTOCOMMIT=True, CONN_MAX_AGE=0
After few hours all posgtress connections are used (too many connections error).
pg_stat_activity is reporting idle connections with part of queries visible.
I would try to deliver more details later.
Change History (1)
by , 5 years ago
Attachment: | Firefox_Screenshot_2020-03-17T15-05-35.104Z.png added |
---|
Note:
See TracTickets
for help on using tickets.