-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maxMemoryRestart in CLI.js #697
Comments
when you do a $ pm2 describe test does it shows
? |
[root@AntColony antcolony]# pm2 describe worker[3002] ⌬ PM2 monitoring : ● worker[3000] [| ] 4 % ● worker[3001] [ ] 2 % ● worker[3002] [| ] 4 % ● worker[3003] [ ] 2 % ● worker[3004] [| ] 4 % After a while, the process will restart(unstable). but if I run lots of ‘worker’, the redis may crash(out of memory). |
Thanks for this feedback. Internally, when setting the maxMemoryRestart option, PM2 set the node v8 argument Looks like an unwanted behaviour form v8 :/ |
Looks like |
We gonna integrate a worker system to monitor and auto restart apps based on a memory limit instead of --max-old-space-size, issue reported to feature list |
+1 |
|
@jshkurti is working on this feature |
I just want to add, that I'm looking forward to this feature. ❤️ 😊 |
This is done :) |
Where to find? |
Then:
The worker runs every 30seconds by default. You can change that by modifying env variable PM2_WORKER_INTERVAL. e.g.
Will force the worker to run every 2 second. |
Thanks! When will it come to master/npm? |
Thanks! |
Awesome! 👍 |
I find the
maxMemoryRestart
in CLI.js, but it is not work, why?pm2 v0.10.7
The text was updated successfully, but these errors were encountered: