Role cannot be reached by Azure-WorkerRole host system

Question

I use Worker Role machines (Medium → 2 Cores with 3.5 GB Ram) to do a huge job, and I can use 100% CPU (both cores) and 85% RAM.

During this work, everyone takes about 20 minutes / 40 minutes when Azure thinks that the machine is unhealthy and stops all my work. In Portal, I see that my working instance receives the message "Waiting for status (role cannot be reached by the host system).

Can anyone know a work that does not include: 1) Use a more powerful role with kernels that I will not use 2) Try to reduce the CPU usage of my application (using 100% CPU is what we want to use)

Thanks in advance Rui

Answer 1

try the following:

Thread.CurrentThread.Priority = ThreadPriority.BelowNormal 

perhaps some other things (processes, threads) also need a lower priority, but this should support 100% processor utilization

for (external) processes, starts them using the following code (this is vb, but you should be able to hide it in your language

 Dim myprocess As New System.Diagnostics.Process() myprocess.StartInfo.FileName = "C:\the\path\to\the\the\process.exe" myprocess.Start() myprocess.PriorityClass = ProcessPriorityClass.BelowNormal 

you can set the priority of the current process of the work role , but it may depend on other processes, so watch out for it , it is better to set the priority of the required process below, this will not slow it down if there is no other work that needs to be done

 Process.GetCurrentProcess().PriorityClass = ProcessPriorityClass.AboveNormal 

Answer 2

This is what affects the service I run on Windows Azure. I just tried manually setting the WaAppAgent priority to high. Hope this helps.

But actually this should not be my problem. Sometimes my database runs on a 100% processor, and this is actually a REAL time to restart.

I really do not want to lay resources, so some heart rhythms will be happy. Do virtual machine instances also have a heartbeat event? Perhaps the solution is to switch to using a virtual machine instead of using the PaaS role?