The Always On setting should have an option to make it sticky to the slot when swapping
This is odd it isn't this way by default but should at the very least have an option to make it sticky so as to not break anyone's current practices (in fact, shouldn't more settings have the option to be sticky?).
The issue here is that an always on slot consumes resources. If for example each app consumes 200Megs of RAM, and I have 5 app services running on a service plan, each app service has 2 slots for swapping, then I need to have Always On turned on unnecessarily for 10 slots (2gigs of RAM consumed for nothing). The only alternative I have is each time after a swap I'd have to remember to turn it on the main production slot and turn it off on the slot I swapped. Cumbersome at best.
Moving the feature request to under review. When we have a clear timeline to share, we’ll update the status.
Great post - vaobong
I think you can mark this one as done now right? I read a blog post a while back that this behavior was changed and according to this documentation this setting is not swapped between slots: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots
I updated my sites months ago to have the staging slot settings for 'Always On' to OFF and it hasn't been an issue any more. I've also just now tested it one more time and it's working well!
Nicely done and thanks!
Nicholas Piasecki commented
Did this actually get implemented with 'Always On' sticky to the slot as the default? It seems I no longer get warned about this. Wonder how long my swap script has been working around this (it used to set Always On = true for staging, swap, then set Always On = false for staging) and not actually doing anything...
Björn Sållarp commented
Not being able to disable this on deployment slots is a huge waste of resources!
15 votes in only 6 weeks, that's not bad. Any updates on this? I guess this is harder than it seems?
Any updates on this? This continues to be a pain point for me.
Thanks for the updates Oded and Ruslan. As a workaround for now, does anyone know if I set Always On=false and use something like uptime robot to ping the site is that sufficient to keep it always on? I read somewhere that it won't work for free accounts, but obviously in this case i'm thinking about using it as a workaround on standard or premium tier.
Hi Mike thanks for feedback. This improvement is in our backlog.