greeting community. I have two instances of PrismaClient in my nodejs application (application lives in ECS contain in AWS if that matters). One client connects to reader db instance (postgres) and other connects to writer db instance. all of a sudden I get

"Timed out fetching a new connection from the connection pool"

which now does not disappear. there is no activity currently in the app but when try to do query get this error. Did anybody face such a problem and if yes what would be possible reason of the problem do get addressed? Any advice would be highly appreciated

@Alexei Snisarenko 👋 Could you try restarting the app on ECS or restart the DB and check if the error goes?

I’m sure it will go and intentionally not restarted to see the root cause

We have seen a couple of messages like this but are unable to reproduce.

I have had a similar issue here @Alexei Snisarenko. If you figure out what caused this, would be curious to find out as well

autoscaling in ECS - will check as well. but not sure how single process should be affected. pool limit is 3 which is far from the available connections on the database. and there was only one process running with unavailable connections. I’ll share results here once find the root cause

Cool, id really appreciate that. Will do some analysis on this later this week as well

Hi @Jonathan. From the moment I did restart the server the problem did not happen to reproduce. Aside from continuing watching over the server I so far do not know the exact circumstances the problem occurs and thus be able to get more information once the problem happens again

Gotcha, thanks for responding back. We will take care that when this happens, we can find a way to reproduce it

Sounds good