CODEWITHSUNDEEP
azuredeploymentazure-functions
Gian C.
Gian C.

Reputation: 179

Azure-Function Deployment kill my running process..can i avoid?

I have a few Azure functions sharing same the code. So I created a batch file for publishing my libs. It is a simple bat file. For each of my azure functions, it connects to a host and uses robocopy to synchronize folders.

However, each time I publish, current running functions are dropped. I want to avoid that. Is there a way to let a running function naturally terminate its work?

I think its possible because when I publish, I'm not re-write real running dll, but I copy file in <azure-function-url>/site/wwwroot folder.

NOTE: The function calls an async method without await. The async method does not completed the work when source change. (Im not focus on this problem, thanks Matt for the comment..open my eyes)

Upvotes: 2

Views: 2072

Answers (1)

Matt Mason
Matt Mason

Reputation: 2724

The functions runtime is designed to allow functions to gracefully exit in the event of host restarts, see here.

Not awaiting your async calls is an antipattern in functions, as we won't be able to track your function execution. We use the returned Task to determine when your function has finished. If you do not return a Task, we assume your function has completed when it returns.

In your case, that means we will kill the host on restarts while your orphaned asynchronous calls are running. If you fail to await async calls, we also don't guarantee successful:

  • Logging
  • Output bindings
  • Exception handling

Do: static async Task Run(...){ await asyncMethod(); }

Don't: static void Run(...){ asyncMethod(); }

Upvotes: 5

Related Questions