sidorares / sidorares/node-mysql2
"read ETIMEDOUT" issues
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.4k
- Forks
- 680
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 59
Description
We've been seeing sporadic read ETIMEDOUT errors when making queries to our database. The traffic is fairly low, and the issue is seen in periods of very low activity i.e. overnight.
These are the particulars:
- Node
22.14.0 - Relevant npm dependencies
mysql2-^3.12.0typeorm-^0.3.20@nestjs/typeorm-^10.0.2
- MySQL 8.0.40 on AWS RDS
- Instance class
db.t4g.large - No RDS proxy
- Instance class
All are on pretty standard config. We've tried setting some of these options but no success
connectTimeout: 30_000
connectionLimit: 40
maxIdle: 10
idleTimeout: 30_000
Are there any configuration options worth trying? AWS seems to suggest there are no issues on their end, very stumped!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reproducing the intermittent timeout with Node 22.14.0, mysql2, TypeORM, and MySQL 8.0.40 using the listed pool settings; done means identifying a reliable cause or configuration change that prevents the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, node.js, typescript
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100