search

Azure / durabletask

Durable Task Framework allows users to write long running persistent workflows in C# using the async/await capabilities.
Apache License 2.0
1.52k stars 295 forks source link

Orchestrator queue fills up but there are no messages on it #207

Open seano288 opened 6 years ago

seano288 commented 6 years ago

We have several environments running durable task orchestrations and in each environment, this behavior is the same. Our orchestrator queue fills up after a few months and all orchestrations then fail. There are no messages on the queue. I'm reaching out to Microsoft support in case this is an Azure issue, but this only happens with our use of the durable task framework, so I'm posting here as well.

Are there any settings I can pass in when creating the task hub worker or client that can address this?

image

simonporter commented 6 years ago

I am still following up on this but my expectation is that the session storage is using up the space. DurableTask keeps the state of a session in a ServiceBus session which is not reflected in the stats above. From a usage standpoint this means you likely have a number of incomplete orchestrations, either they are waiting for a notify event or they are in a state waiting for a timer to fire.

DonDavio commented 5 years ago

Any update on this issue? We're assessing DurableTask for potentially thousands of long-running (months/low years) orchestration instances. Is that not a supported use case?