How to restart ASUS App App Instance

I have an Azure application service that contains 1 web application with 1 slot. I have 2 instances assigned to the App service. This week, the App Service shows about 60% of CPU usage and is usually around 10-15%. With further research, it seems that one of the two copies is exceeded. When I open the site metrics for each instance, I see that the HTTP response time is 1000 milliseconds for one instance and less than 200 ms for another. I tried restarting the W3P process on a corrupted instance, but that doesn't seem to help. I also tried expanding to additional instances. New instances look good, but when I shrink back, the fabric will not kill the offending instance.

How to make a tissue controller kill a specific instance?

I found the powershell AzureRestartRole command here ( https://msdn.microsoft.com/en-us/library/azure/dn495202.aspx ), but my Azure Powershell Command Prompt command does not seem to recognize the command, so I tried switching to Azure SDK 1.3 using the install-module command, but the AzureRestartRole command was not found.

+13
source share
2 answers

I recently ran into a similar problem (one bad instance always read zero from ConfigurationManager.AppSettings , while the other instance was fine). I found that you can restart a specific instance of the Azure Application Service (web application) from the Azure portal .: D

Updated on August 16, 2019:

The short version is that if you go to the portal for your web application in the Diagnostics and Problem Solving section, find ** Advanced restart of the application *, and you will get an option that allows you to select only the instance that you want.

hope this helps

+24
source

the command code you specify should not be used with Azure App Service, but with cloud services and role-based applications, so you do not need it here. Azure SDK 1.3 is also very old, today the most recent is 2.9.

Then try using the Auto-Healing function - it’s hard to understand why your web application uses resources so, especially if you tried to restart W3WP (did you kill it in the process explorer in the control panel?), So the built-in function can be useful.

And you can find the webapp id and execute PowerShell , for example, stop and start it. If this does not help, I would suggest re-creating the instance.

+2
source

All Articles