Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PoolError: connection pool exausted #13

Open
guytamir1 opened this issue Jan 9, 2014 · 3 comments
Open

PoolError: connection pool exausted #13

guytamir1 opened this issue Jan 9, 2014 · 3 comments

Comments

@guytamir1
Copy link

Hey there,

Started working with django-db-pool.
Once I changed the settings and deployed to Heroku I saw immediate improvements in response times.

For some reason when I'm running in dev mode on my machine I'm getting
PoolError: connection pool exausted

This happens on the second time I try to query the DB.
First time I log in (check DB for data) and all is well, when the next page loads I get the error..

Same code is running great in production..
Any ideas?

@gmcguire
Copy link
Owner

gmcguire commented Jan 9, 2014

How are you running django on your dev machine? What pool options are you using?

@guytamir1
Copy link
Author

running with foreman.

Update - the same problem now happens in production.
Not using any special pool options (Using autocommit - not sure if relavant)

@gmcguire
Copy link
Owner

Depending upon your app server's process/threading model you may need to raise the number of connections in the pool for each process. See the MAX_CONNS parameter in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants