Feature Request: Startup priorities / delayed start

neophob commented 6 years ago

Thanks for pm2! really like it, but I miss one feature:

Think about your low end device starts 4 microservices as soon the device is started. starting a node application might be resource intense (parsing node_modules) - so the startup is not really deterministic - but you might want microservice#1 is started before all other microservices.

I have some ideas how to resolve this:

add a bootdelayMs option, this (static) delay is applied the first time the application is started. might be the easiest to implement
bootstrapCap option, this setting defined that maximal bootstrapCap processes are allowed to be started. might need another option to define the priority (bootstrapPrio)

any other ideas how to improve the startup processes?

ksugiarto commented 6 years ago

I need this feature as well. And this is important for several cases

intensite commented 5 years ago

We would need this as well !!

We have an IoT application running 4 micro-services on a RaspberryPi. 3 out of the four micro-services requires the first one to be started and operational. The problem is that some of those may start before service number one startup is completed.

As the original poster suggested, some kind of delayed start or a startup priority would be a great addition to this amazing program :-)

sdancer75 commented 3 years ago

me too

zackees commented 5 months ago

I too needed this feature a bunch of times.

Unitech / pm2

Feature Request: Startup priorities / delayed start #3685