Durable Functions

Question

I'm pretty new to Durable Functions.&nbsp; I have a question regarding terminating them.&nbsp;So we have an application that iterates through azure storage blobs.&nbsp; 0-n # of blobs where n is pretty much unbounded.&nbsp;&nbsp;So The orchestration takes the blobs, iterates and does actions against them.&nbsp; Since I come from java, the way that this was implemented was through each iteration, each blob will return 500 items and it will spin off a java thread to do the work.&nbsp; When it hits the thread cap, it will wait until a thread is freed up to continue doing the work.&nbsp;The question I have is, when I try to terminate this, I've noticed that it will be terminated, and won't list it as running anymore, but looking at the live logs, the threads are continuing to do their work.&nbsp; &nbsp;When we terminate something, do we need to implement some interface so the threads can be interrupted?&nbsp;Or am I going about this entirely the wrong way and the threads should be removed in favor of async tasks/fan out.&nbsp;&nbsp;

kidd_ip · Answer

Try this to in C# to implement cancellation tokens in your activity functions
&nbsp;
public async Task MyActivityFunction(CancellationToken cancellationToken)
{
    while (!cancellationToken.IsCancellationRequested)
    {
        // Perform work here
    }
}
&nbsp;

nghiale-tr · Answer

Thanks for the reply.&nbsp; Yes, I think I need to refactor my entire application to use async Tasks, then orchestrate the functions.&nbsp; As the way I'm doing them with Threads doesn't seem to match the way it was intended to be used.

Forum Discussion

Durable Functions

2 Replies

Resources