Azure Front Door - How to do rolling update of backend pool?

5
votes

Has anyone successfully done rolling updates with Azure Front Door? We have an application in 2 regions, and we want to disable the backend in region 1 while it gets updated and same for the backend in region 2. However, there seems to be a ridiculous amount of lag time between when you disable or remove a backend from a pool, making this basically impossible.

We've tried:

  • Disabling/totally removing backends
  • Setting high/low backend priorities/weights
  • Modifying health probe intervals
  • Changing sample size/successful samples/latency to 1/1/100

I have an endpoint that I watch during the deployment process which tells me which region it's in, and it never changes during the operation, and becomes unavailable when the region is being updated. There's gotta be a way to do this, right?

1
azureload-balancingazure-front-door
Original post was 2 years ago but doesn't look like Front Door delays in config changes has improved. I was looking into these delays today and fud adding/removing backends took over 30mins to take affect. camerondwyer.com/2021/07/16/… – CamD

1 Answers

0
votes

I have a suggestion,

  1. Reduce the Health Probe Interval.
  2. Reduce the sample size and successful sample required. (Make sure you are probing to a simple HTTP page so your backend resource can handle the loads. You will start receiving probes from all the POP servers with the interval you specified.) 3.For the sever which you need to do maintenance, stop the service or make the probe fail, so that all traffic will switch to the healthy server. Then do the maintenance and start the service again. This will make sure your service is not disrupted.