Minor bug fix
This update includes a minor bug fix that automatically handles reconnections when receiving the occasional EPIPE error. Special thanks to @kernwig for the PR.
Full Release Notes: https://github.com/jeremydaly/serverless-mysql/releases/tag/v1.5.4
NPM: https://www.npmjs.com/package/serverless-mysql
GitHub: https://github.com/jeremydaly/serverless-mysql
Did you like this post? 👍 Do you want more? 🙌 Follow me on Twitter or check out some of the projects I’m working on.
Learn more about Serverless MySQL or check out the other projects I'm working on.
I’m using serverless-mysql node module to insert log records into MYSQL database which is installed on a remote server from my AWS lambda function . It’s running live now. But sometime, I got one error while inserting the records into MYSQL , which is read ECONNRESET. Can you advice me, how to handle such scenarios using that serverless-mysql module?
How many available connections do you have on your MySQL database? This typically happens when you are aggressively cleaning up connections that are still being utilized because you don’t have enough connections available for your workload. The library can help in times of heavy load that exceed total connections available, but that should be the exception, not the rule. If you expect 500 concurrent connections, you should have at least that available on your DB.
Getting read ECONNRESET error on inserting records into remote server MySQL database. Please advice.