OrchestrationTrigger持久功能:Azure Function App Consumption的输入和执行时间 [英] OrchestrationTrigger Durable Function: input and execution time with await with Azure Function App Consumption

问题描述

我遇到了以下链接，并有疑问:

I came across the link below, and have questions:

https://docs.microsoft.com/zh-CN/azure/azure-functions/durable/durable-functions-checkpointing-and-replay

1当调用OrchestrationTrigger持久函数时，由于某种原因而崩溃(例如，最大超时持续时间为10分钟后)，将从表存储或队列中自动读取下面的输入names.

1 When an OrchestrationTrigger Durable Function is invoked, and crashes for some reasons (e.g. after max timeout duration of 10 mins), will the inputs, names, below be read from table storage or queue automatically.

[FunctionName("E1_HelloSequence")]
public static async Task<List<string>> Run(
    [OrchestrationTrigger] DurableOrchestrationContext context)
{
    var names= ctx.GetInput<List<string>>();

    var outputs = new List<string>();

    outputs.Add(await context.CallActivityAsync<string>("E1_SayHello", names[0]));
    outputs.Add(await context.CallActivityAsync<string>("E1_SayHello", names[1]));
    // returns ["Hello Tokyo!", "Hello Seattle!"]
    return outputs;
}

2崩溃后，它将自动重新启动.

2 After it crashes, will it re-start automatically.

3在每次等待时，该功能都转换为等待状态，等待时间是否占最大超时持续时间的一部分?

3 At each await, the function transits into wait status, does the wait period contribute to part of max timeout duration?

推荐答案

您好，功能产品小组的克里斯已经在

Hi as Chris from Function Product Group is already involved with you on GitHub Thread. Posting it here so that it is beneficial for other members as well.

1)是，将从表存储中读取任何已执行活动功能的结果.

1) Yes, the results of any executed activity function will be read from table storage.

2)是，该功能将自动重试.现有的队列消息可确保这一点.

2) Yes, the function will retry automatically. An existing queue message ensures this.

3)不，等待时间不计入您的最大功能超时.你也不是 计费等待时间.

3) No, time spent awaiting does not count against your max function timeout. Nor are you billed for time spent awaiting.

这篇关于OrchestrationTrigger持久功能:Azure Function App Consumption的输入和执行时间的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！