Hello. We have deployed our Node.js application on AWS ECS, with AWS RDS for MySQL. We have not tuned the

connection_limit

parameter, nor any other parameters. We accepted the default ones. Our ECS instance has 0.5 cores available with one instance (in the development environment), hence, the connection limit would be

2 * 0.5 + 1 = 2

for our instance. However, while monitoring RDS, we notice a warning in our database. Here's what the warning said:

[Warning] Aborted connection xxx to db: '<database name>' user: '<user name>' host: '<host IP>' (Got an error reading communication packets)

I hope the given information is sufficient to know about the problem we are facing. Otherwise, I am happy to share more details if required. Thanks!

The error doesn’t necessarily imply the box is out of connections. Is the warning appearing frequently?

Yes, it appears quite frequently. By querying the

information_schema.PROCESSLIST

table, we noticed that Prisma keeps the process in sleep until the configured TTL in RDS limit is reached (i.e. 300 seconds). Our team suspects this may be causing the issue.

Please open a ticket here: https://github.com/prisma/prisma/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml

👋 Hello @Dhwanik Panchal - did you end up opening the GitHub issue and resolving this problem? Let us know!