Wrong connection pool info ??
On production my queires stopped working with error
Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 9)
but actually im on DigitalOcean with another configuration showed on picture.
and i have "&connect_timeout=300" in connection string
Connection pool | Prisma Documentation
Prisma ORM's query engine creates a connection pool to store and manage database connections.
2 Replies
Hello @Aleksandar Dimitrijevic 👋
How many db connections are supported by the database?
Can you run
SELECT * FROM pg_stat_activity SQL and check which apps are occupying the connection?
Can you try adding pool_timeout instead of connect_timeout?
https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/databases-connections/connection-pool#setting-the-connection-pool-timeoutConnection pool | Prisma Documentation
Prisma ORM's query engine creates a connection pool to store and manage database connections.
i increased connection_limit through connection string and errors went away
to 20.
i have 5 different apps hosted on kubernetes with 2 replicas
so 10 apps basically are connected to same database.
i was just confused about Digital ocean pool, with size 350.
What should I do to make full usage of that ? Am I supposed to change connection_limit, even tho i go with connection string for that DigitalOcean Pool i still have problem.
Is there a difference about connection_limit and that DO pool size, maybe I'm understanding something wrong
f