We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We recently upgraded from 95d1102 to the release version, and started seeing a lot of the following message from our Celery workers after a deploy:
PoolError('connection pool exausted', )
Switching to MAX_CONNS: 2 alleviated the problem.
Have switched back to that rev, and it's all working fine now. [Django 1.5.4]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We recently upgraded from 95d1102 to the release version, and started seeing a lot of the following message from our Celery workers after a deploy:
Switching to MAX_CONNS: 2 alleviated the problem.
Have switched back to that rev, and it's all working fine now.
[Django 1.5.4]
The text was updated successfully, but these errors were encountered: