azure-durable-functions

问题 We have lots of files that get created in blob storage and consequently we are passing these files to the azure functions. However with Azure function and event grid trigger it was timed out after certain no. of files were processed. Hence now I am trying with durable functions. Below is the code I tried. ProcessJob_EventGrid gets triggered. However the ProcessJob_Orchestrator never gets triggered. Is there something that I am missing. I am completely new to the Durable functions concept.

问题 Problem I have a C# Durable Azure Functions app (v2) containing an orchestration and activity function. The orchestration calls the activity as follows: propBag.CE = await context.CallActivityAsync<CEData>(nameof(GetCEByExternalIdActivity), propBag); The call works ok and the Activity function executes, builds up the content for propBag.CE and returns. The CE object contains a few other objects, including: public List<IParty> Individuals { get; set; } public List<IParty> Organisations { get;

问题 I can see azure durable functions uses a storage account for managing state and instrumentation. When running durable functions in an environment with a high amount of data tables and queues will get larger and larger, and properly slower and slower. Does durable function clean logs them self, or is this a task you need to do your self? 回答1: After researching this, it appear that it's up to the developer to implement their own handler for this. I read through the github issue the accepted

问题 I can see azure durable functions uses a storage account for managing state and instrumentation. When running durable functions in an environment with a high amount of data tables and queues will get larger and larger, and properly slower and slower. Does durable function clean logs them self, or is this a task you need to do your self? 回答1: After researching this, it appear that it's up to the developer to implement their own handler for this. I read through the github issue the accepted

问题 I can see azure durable functions uses a storage account for managing state and instrumentation. When running durable functions in an environment with a high amount of data tables and queues will get larger and larger, and properly slower and slower. Does durable function clean logs them self, or is this a task you need to do your self? 回答1: After researching this, it appear that it's up to the developer to implement their own handler for this. I read through the github issue the accepted

问题 We're using a Durable Orchestrator Function that needs to make several million calls to Activity functions. We're seeing the following exception after 100,000 invocations: Maximum amount of orchestration actions 100,000 has been reached. This value can be configured in host.json file as MaxOrchestrationActions. However, I cannot find HOW to set this value. In the host.json schema here, it's not specified. I've pulled the head of the dev branch for Azure Function Durable Extension and traced

来源： https://stackoverflow.com/questions/64053513/what-happens-to-durable-functions-after-activity-function-gets-called

问题 I used a v2 azure function (durable function) with custom dll (.net core 2.2) that calls a service and I get the following exception: Could not load file or assembly 'System.Private.ServiceModel, Version=4.1.2.4, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' In the debugging process, I can't step into the method and the exception is thrown without letting me inside it and I don't know exactly what tried to access that library. Putting manually the package from .nuget in the bin folder

问题 I am trying to track down some occasional Non-Deterministic workflow detected: TaskScheduledEvent: 0 TaskScheduled ... errors in a durable function project of ours. It is infrequent (3 times in 10,000 or so instances). When comparing the orchestrator code to the constraints documented here there is one pattern we use that I am not clear on. In an effort to make the orchestrator code more clean/readable we use some private async helper functions to make the actual CallActivityWithRetryAsync

问题 I’m a big Domain Driven Design fan and developer, and am always attempting to map technology/architecture into the world of DDD. Mapping microservices to bounded contexts provides for a natural marriage. At the end of the day, I just want to focus on my business logic and host that in the right environment. Durable Functions looked promising to me, in needing to solve the distributed transaction problem across microservices, Sagas or Process Manager if you will. I have been using NServicebus