[Django]-RabbitMQ keeps connections running for a long time

1👍

Was able to fix this by adding BROKER_POOL_LIMIT=0 to my production settings.

0👍

BROKER_POOL_LIMIT=0 means any part of your setup that needs a connection will establish it, do its thing and disconnect

while this helps with idle setups, you will find yourself sporadically hitting that 6 connection limit during periods of higher traffic, because you simply need more than 6 connections for all your stuff to talk to cloudamqp

check out heroku celery exceeding connection limit for an explanation of why and how to fix it

Leave a comment