PM2 not reflecting changes after modifying file
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
PM2 not reflecting changes after modifying file
Steps to reproduce:
I run approx 25 servers running 4 instances/clusters each on Windows running on a 4 core CPU.
After I make any change on any file it restarts the respective server, however it doesn't reflect new changes and continues to show old changes only.
Then I am forced to do the following steps for the changes to reflect.
$ pm2 stop all
$ pm2 kill
$ pm2 start... (one by one)
Supporting information
OS: Windows
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 source file, test, PM2 version, or exact command sequence is named. Start by reproducing the behavior on Windows with clustered instances, then compare a file change after the automatic restart with the stop/kill/start sequence; done means updated code is loaded without manually stopping and killing all processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100