During this time, I will be deploying an update to Aether which will remove the reliance on pm2's instance id for determining which process is which cluster. Instead, it will just assign the first available cluster id.
This has been tested locally and has worked flawlessly but as always issues may arise in production for the sole reason of it being in production so I will have an instance of Fire that doesn't connect to Aether ready to boot up if any issues occur to minimise downtime.
I will also be deploying a small change to Fire's ecosystem file (https://pm2.keymetrics.io/docs/usage/application-declaration/
) that adds an exponential backoff for restarts if an error occurs and adds a max memory restart of 1GB.