Hi folks, apologies if this is not the correct forum for questions, but I did not want to raise an issue if it's unrelated to Prisma. I've had Prisma running for a week now against Aurora Serverless V2 (_8.0.mysql_aurora.3.02.0_). However, I'm noticing my logs are getting spammed with the following, and I've no idea why this might be.

2022-05-09T12:25:07.783788Z 1568 [Note] [MY-010914] [Server] Aborted connection 1568 to db: 'xxxxxx' user: 'xxxxxxx' host: 'xx.xx.xx.xx' (Got an error reading communication packets). (<http://sql_connect.cc:835|sql_connect.cc:835>)

AWS documentation has a few possible solutions for this fairly common mysql issue listed here: https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-communication-packet-error/ - you should also look into connection pooling as well (if you aren't already).

Interesting! I did come across this article but am having a hard time figuring out the root cause and if that was Prisma or a misconfiguration! I'm not currently using any external pooling solutions as I'm not sure of a production-ready solution that I could use with Aurora Serverless V2. FWIW, I'm currently running Prisma from Next.js API Routes @ Vercel

Did you try changing the timeout value through the pool_timeout parameter and check if that fixes this?

Hi @Nurul - I did, these are my settings

?connection_limit=5&pool_timeout=20

however I am still seeing the issue... I also tried a

connection_limit=1

that’s strange, so these logs were not produced earlier but only recently started, did you make some changes to the schema file or perhaps updated

@prisma/client

version?

So this is my first time using Prisma; it's a fresh Aurora Serverless v2 MySQL database with a basic schema, as well as the most recent Prisma client. The errors appear to start soon after I visit my application and a connection is made and they have been present for the whole week since deploying

It could be an Issue with Aurora Serverless V2 as well, I think it was released in GA quite recently, it used to be in beta before.