My Web Service typically uses approx 20 connections to my Redis. However, while deploying, both are simultaneously connecting, and I will sometimes temporarily exceed the 50 connection limit while the new release is loading up and the old release is still running.
Are there any steps I can take to avoid the errors I’m getting on launch when the connection limit gets exceeded? Is there any way the Redis can now that this is a brief replication of connections and to temporarily allow the new connections before the old dying connections go away?
Hi there,
Because of the limit of our free plan free of 50 connections you probably want to reduce your Redis counts so that zero downtime deploys don’t push you over the plan limit. That, or change your plan to have some spare capacity.
Regards,
John B
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.