[Question] Is pm2's cluster mode restarted all the time? Will it affect my timer?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
I'm a newbie,
I've noticed that pm2's cluster mode keeps restarting several processes (the log keeps printing the start command)
I made a call to a third-party API in my project. After successful call I used setTimeout or setInterval to get the result. So if the process is restarted, will my setTimeout/setInterval be gone?
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
This question names no files, tests, or entry points. Start by checking PM2's cluster-mode restart behavior and Node.js timer lifecycle; done would be a clear answer explaining whether a worker restart loses its setTimeout/setInterval state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100