CODEWITHSUNDEEP
google-cloud-platformgoogle-cloud-run
deniable_encryption
deniable_encryption

Reputation: 149

Mitigating Cloud Run's limitation regarding Cloud SQL connections per instance

I link my Cloud SQL instances to Cloud Run with the --add-cloudsql-instances argument.

Some requests are getting 500 Internal Server error in it's responses. Looking at the logs, I was able to know that Cloud Run "Exceeded maximum of 100 connections per instance...". I know that Cloud Run limits to 100 the number of connections that each Cloud Run instance can do to Cloud SQL.

I have already tried to set lower concurrency levels in my Cloud Run service as a way to avoid each instance from exceeding the limit, but the problem never dies. What can I do to mitigate this behaviour and bring my application back to normal stability?

PS. I can't find good and recent answers on this anywhere in the internet, so I decided to ask here.

Details about my last Cloud Run revision: 4 vCPUs, 6GB of RAM, --concurrency of 32.

Upvotes: 1

Views: 985

Answers (2)

John Hanley
John Hanley

Reputation: 81454

With a concurrency of 32, and a connection limit of 100, you have a connection problem. You are either not closing connections before returning an HTTP response (leaving unused connections) or you are opening more than one connection per HTTP request and possibly not closing them.

You will need to do a code review for database connection handling.

Opening database connections is an expensive operation. Opening more than one connection per HTTP request consumes time and resources. Use Connection Pooling to resuse connections to increase performance and prevent exhausting open connection limits.

Upvotes: 3

slbinilkumar
slbinilkumar

Reputation: 1

Restrict the load to your application by setting a HTTPS load balancer.

Upvotes: -1

Related Questions