DTFxClient.GetOrchestrationStateAsync() takes longer than expected

Open
#1,037 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp

Research direction

Start with the DTFxClient.CreateOrchestrationInstanceAsync call shown in the report and trace why awaiting its task can take 3–5 minutes; the title also names DTFxClient.GetOrchestrationStateAsync. Reproduce the reported latency if possible, identify the responsible path, and verify that orchestration instances can be queued without the reported delay.

Written by the indexing model from the issue text.

Description

Hey, we are using DTFX for async job, but we are getting significant latency while creating orchestration instances.

"Task task = DTFxClient.CreateOrchestrationInstanceAsync(
NameVersionHelper.GetDefaultName(orchestrationType),
NameVersionHelper.GetDefaultVersion(orchestrationType),
instanceId,
input,
tags,
dedupeStatuses);

var result = await task;"

We are awaiting on the task so that it can give guaranty to the caller that instances have been queued. But that await is causing latency to shoot up as in worst case we are getting max delay of 3 to 5 mint for this task to finish.

Dominant language
C#
Stars
1.7k
Forks
335
Avg merge
4d 2h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/durabletask

All issues in Azure/durabletask

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.