Hi @jminns90 ,
During a server upgrade, you must stop the AlteryxService on all of your nodes, which is sufficient for all schedules to be disabled.
I suggest reading these topics before your upgrade since important guidelines must be followed.
https://help.alteryx.com/20223/server/install-or-upgrade-server
https://help.alteryx.com/sites/default/files/2023-02/Server%20Upgrade%20Checklist_v3.pdf
Best regards,
Fernando Vizcaino
The only problem with this approach is that if there is a MongoDB upgrade then that automatically attempts to re-start the service even if you have not completed the upgrade e.g. by applying patches or installing predictive tools.
At that point the system will grab any queued jobs and attempt to run them. Some of our jobs take 6-8 hours to complete...
Because the Alteryx service manages the website as well as the engine it also provides a window for users to log on during the upgrade process. To prevent that we appear to have to set up a temporary firewall rule or disable DNS.
Seems we are left with no alternative but to disable each schedule individually and then re-enable them again?
That also means recording any schedules that were disabled for other reasons prior to the upgrade.
Can we not just have a maintenance mode for upgrades please?
Hi @Paul_Holden ,
You are 100% correct. I think I misread the question or didn`t consider the whole picture when answering this question.
I also struggle with this, especially when making a copy of PROD to our DEV (host recovery). I always need to remember to turn off the schedules before restarting the server by accessing Mongo directly.
Best,
Fernando
It would be really helpful to have an option that suspends the scheduler separately to having to stop the Alteryx service. Just so much cleaner that way?