You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I quickly hacked the production server to increase consumer_timeout from the default 1,800,000 ms (30 mins) to 10,800,000 ms (3 hours) so that I could run longer transition state optimization calculations.
Along the way I learned that in v1.9+ of Rabbit they are doing away with the docker-specific environment keywords I use. At some point I should update rabbitmq to run on this new standard: https://hub.docker.com/_/rabbitmq (see section Environment Variables).
For now I manually added the rabbitmq.conf file on dev/prod servers. I updated the docker-compose.web.yaml file in the code base.
The text was updated successfully, but these errors were encountered:
I quickly hacked the production server to increase
consumer_timeout
from the default1,800,000
ms (30 mins) to10,800,000
ms (3 hours) so that I could run longer transition state optimization calculations.Along the way I learned that in v1.9+ of Rabbit they are doing away with the docker-specific environment keywords I use. At some point I should update rabbitmq to run on this new standard: https://hub.docker.com/_/rabbitmq (see section Environment Variables).
For now I manually added the
rabbitmq.conf
file on dev/prod servers. I updated thedocker-compose.web.yaml
file in the code base.The text was updated successfully, but these errors were encountered: