PrismaP
Prisma•12mo ago•
6 replies
Infamy

Issue with Prisma Pooling Timeout

Hello everyone, new poster here. I am pretty new to Prisma and have had no issues in recent months with it. Today my production server just started stating:
Rate limit check failed: Error [PrismaClientInitializationError]: 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: 3)
    at async n.checkRateLimit (.next/server/app/api/agents/create/route.js:1:4293)
    at async Object.authorize (.next/server/app/api/agents/create/route.js:1:5366)
    at async Object.c (.next/server/chunks/712.js:25:4504)
    at async g (.next/server/chunks/712.js:1:105587)
    at async a (.next/server/chunks/712.js:25:18496)
    at async e.length.t (.next/server/chunks/712.js:25:19986) {
  clientVersion: '6.1.0',
  errorCode: 'P2024'
}


I have now tried what feels like 100 different options to fix this. To explain the same setup locally does not experience this issue. I have changed the server instance to one with more memory as I noticed issues with metrics but now that it has more overhead it does not seem to be the issue. I have tried changing my connection string and adding connection_limits, enabling and removing pgbouncer which my serverless DB provider states in the connection string. I am really struggling now to work out what the issue is, It works fine locally as I have said but on the production server it has just stopped working within the last couple days... Anyone have any idea or advice on what to go on here?
Was this page helpful?