node-red / node-red/node-red-nodes
"Error: read ETIMEDOUT"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Hi, I've been using node-red-node-mysql for almost a year in a Node-Red instance created as Cloud Foundry app in IBM Cloud. The node worked fine with several MySQL DB from ClearDB. The MySQL ClearDB DB also were generated through IBM Cloud as a service. Since IBM Cloud announced that ClearDB will no longer run as a service, I migrated these DB to new MySQL of ClearDB. Since then I noticed that several data is not been inserted into the DB and usually followed by "Error: read ETIMEDOUT". What does mean? How can I fixed this problem? The Node-Red version is v0.17.5 and the noder-red-node-mysql version is 0.0.17.
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
Start by reviewing the node-red-node-mysql package at version 0.0.17 and the reported Node-RED v0.17.5 environment, then reproduce the timeout after migrating from the IBM Cloud ClearDB service. Done means identifying why inserts fail with "Error: read ETIMEDOUT" and documenting or verifying a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mysql
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100