Geek Answers Handbook

Is there a hard limit on how long the Azure role can run?

Suppose I include a rather lengthy launch task in my Azure role - to run something like a few minutes. What happens if the launch task takes too long.

I am currently testing Compute Emulator and am observing the following.

I have a 450 megabyte .zip file with Info-Zip unzip . The launch task unpacks the archive. The launch starts and I look in the task manager. Numerous service processes are launched, then unzip.exe is launched. After about two minutes, all these processes are stopped, and then restarted, and unzip.exe starts again.

So, it seems that the deployment is allowed to work for about two minutes, then forcibly reset and starts again.

Is this the expected behavior? Does it persist on a real cloud? Are there any strict limits on how long a role can run? How to resolve this situation besides moving the unpacking to RoleEntryPoint.OnStart()?

+5
source share
4 answers

, . Startup Task - taskType = "simple", - 50 . Fabric , . " " , 50 , , - .

, , Startup ! 50 .

+7

, (, 20-30 ), "". , , , ( ). FC , "" (.. ).

dev , . "keep waiting", "" . , ().

, , . , , 3 -, , ...

+1

, Azure Fabric . (, ), , .

You can try running the startup process in a background thread that runs independently. This should help you avoid reusing the role during the startup process. Just keep in mind that you may need to make some adjustments if you receive requests before this role is fully operational. There's also a way (which I can't remember ATM) to mark a role and take it out of load balancing temporarily until your process is complete.

0
source

More articles:


All Articles