Durable orchestrator stuck in pending state for around 20.30 seconds frequently when function app scales to multiple instance #2052
Unanswered
ashishsure
asked this question in
Q&A
Replies: 1 comment
-
It's probably caused by queue polling delays, which is normal when your app has low load, and you scale out to multiple app instances. This behavior and potential workarounds are described in our documentation, here: https://docs.microsoft.com/azure/azure-functions/durable/durable-functions-perf-and-scale#orchestration-start-delays |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I want to understand why does orchestrator gets stuck in pending state when there are multiple instance running either in consumption or in Premium Plan?
How can we fix this ?
Beta Was this translation helpful? Give feedback.
All reactions