You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for me, the solution for this is to run pm in fork_mode, by adding the paramenter -X to pm2.
please note that i am running a single core ec2, so basically, for my case, there is no difference in using cluster_mode or fork_mode.
would grunt-ec2 benefits of adding the param -X (through conf) when runing pm2? or other issues can happen by adding this features?
please let me know and if you think this can be an improvement, and in case of yes, I will PR
thx
The text was updated successfully, but these errors were encountered:
Yes. This sounds like the sensible thing to do. FWIW I moved to using bash scripting instead, and in that version of the same code I use recluster to get cluster functionality with hot code reloads.
i have just started using pm2 and gunt-ec2 and i have incurred in a a bug with pm2.
the bug is reported here:
Unitech/pm2#731 (comment)
Unitech/pm2#74
for me, the solution for this is to run pm in fork_mode, by adding the paramenter -X to pm2.
please note that i am running a single core ec2, so basically, for my case, there is no difference in using cluster_mode or fork_mode.
would grunt-ec2 benefits of adding the param -X (through conf) when runing pm2? or other issues can happen by adding this features?
please let me know and if you think this can be an improvement, and in case of yes, I will PR
thx
The text was updated successfully, but these errors were encountered: