Application Gateway management operations are agonizingly slow
[Originally posted to Azure Portal forum - however should have been submitted here]
Most creates and updates for application gateway configuration (back-end pools, rules, listeners, certificates, etc.) take 5-10 minutes to apply. This is not a portal issue as it takes just as long via the API / CLI. (This is with even a single instance App Gateway)
Applying these same settings on Windows Server ARR directly takes only a minute or less, so I'm not sure where the performance issue lies, but there is tremendous room for improvement.
As it is currently, it provides waaaay too much time while waiting to consider the porting costs of a migration to the alternate cloud platform.
Kevin Piette
shared this idea
Update operations have been enhanced with fast update. The operations which continue to be slow are SSL Policy, SSL certificate, ports and scaling up/down. Most other operations like listener, rules, http settings, backend pool, backend pool members, probes should be of the order of ~1min now.
125 comments
-
Ryan Malayter
commented
This is NOT "completed" if a simple port change still takes 10+ minutes.
-
[Deleted User]
commented
This isn't complete, its so slow I could standup alternative infrastructure on another provider and migrate services in the time it takes to swap a certificate on a listener.
-
Rich
commented
Why is this thing still so dreadful?
-
Mateus Attie
commented
I have the same issue. Changing a simple attribute takes more than 10 minutes to complete the apply task on azurerm_application_gateway resource. Any updates on this issue ?
-
Peter Henggeler
commented
Is there any traction on this? Update times take forever to remove a server from a backend pool and then add a server back to a backend pool. What do other folks experience as the average time to make these changes?
-
Ronald Buys
commented
I created a complicated APGW ARM-template but I have the same issue as Peter Drozdowski.
Today I will try to find out why the engine is not completing my deployment since the settings are there. The 'InternalServerError' doesn't tell me anything, I will see if I can reduce options in my ARM-template in order to fix the 'InternalServerError'.
-
Peter Drozdowski
commented
We recently build a terraform pipeline to deploy a simple application gateway v2 (with auto scaling). The pipeline runs for exactly 31 minutes every time and always throws an 'Internal Server Error' at the end. The resource actually gets created, but its always in a 'Failed' state.
Code="InternalServerError" Message="An error occurred." Details=[][0m
[0m on main.tf line 29, in resource "azurerm_application_gateway" "application_gateway":
: resource "azurerm_application_gateway" "application_gateway" [4m{[0m -
EXT SA Petrovs Artjoms
commented
All operations started to take more than 3 hours to complete out of a sudden (App Gateway V2).
Did anyone find a permanent solution to resolve this issue? -
Chakravarthy Balagani
commented
Backend pool update runs for 60 min and exited with Operation Cancelled error but in the portal it still shows 'Updating' on App Gateway.
Not able to run any further commands on the gateway as existing operation is still in progress..
-
Anonymous
commented
My experience:
I'm doing "az network application-gateway create --sku Standard_Medium" and is taking 2 hours and counting. While that is ongoing, I created a new one with --sku Standard_V2 and it took only 3 minutes. So it seems the COMPLETE status here does not include the Standard tier.
Just before posting this, it finished and output was...
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "InternalServerError",
"message": "An error occurred.",
"details": []
}
] -
Anonymous
commented
I have updated rule in app gateway, its taking time since 40 min. Any Idea what to do with this, or any alternative which can help me to do further updates because it's not letting me to work further
-
Anonymous
commented
i have same issue, more than an hour and still trying to delete a very lightweight appgw
-
Srinivas Gopishetty
commented
My feelings are same. Very slow in creation and Updates. it takes at a minimum 10 mins for even simple changes like changing port.
-
Duray Akar
commented
It completed in 48 minutes
-
Duray Akar
commented
It has been 27 minutes and still waiting for an SSL Cert update on the listener.
How is that for COMPLETED? -
Nuno Serrenho
commented
This is not completed. Still agonizingly slow to add a Listener, Rules. Making a single change sometimes takes 15-30 minutes.
-
Brendan Kamp
commented
Still battling with this, how do companies like Kong create a solution that's so quick (and I'm not even a fan of kong) to make changes to but Microsoft it takes 50 minutes to add an https listener? and if you make multiple changes through the UI they cancel each other out?
-
Daniel Pupek
commented
Not completed....It takes foreveer for some updates and I frequently recieve "Operation was superseded by a subsequent update on application gateway" when updating a rule
-
Mike
commented
This is not completed, at all. Still very slow updating some listener, probe settings in v1 gateway
-
Isa Neil
commented
over an hour to delete an app gw... still going.