2 Answers
- Newest
- Most votes
- Most comments
0
If you can see/change the code of the Lambda function, check a connection timeout, for example:
// Example Prisma timeout setting
const prisma = new PrismaClient({
datasources: {
db: {
url: 'mysql://username:password@proxy-endpoint/database',
timeout: 60000 // 60 seconds
}
}
});
Check Aurora Parameter Group Settings
- idle_in_transaction_session_timeout: 1h
- statement_timeout: 60s
- max_connections: Set according to your load requirements.
Ensure that your RDS Proxy is correctly configured to handle connection pooling and failover:
- Max Connections: Ensure that the max_connections setting on the proxy is set to a value that can handle the expected load.
- Target Health: Check the health of your Aurora targets in the RDS Proxy configuration to ensure they are healthy and can accept connections.
0
Appreciate the answer. I am actually not seeing that Prisma has that functionality. What docs are you referencing for that feature?
Also, are you suggesting that these settings between Prisma and Aurora/RDS are causing problems with eachother? I would be interested to hear more about this.
answered 4 months ago
Relevant content
- Accepted Answerasked 2 years ago
- asked a year ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago