Open justinm0 opened 9 months ago
Which App Service plan are you using? If you are only using a single host (and you have no external Orleans clients), you could try with UseLocalhostClustering()
We are using a Windows app service plan on sizes S1 or S2 in South Africa North.
I discovered that the app was being automatically restarted because it wasn't starting up in time, which is not fully Orleans's fault, although Orleans does add to the startup time. I increased the startup timeout through web.config and the site now starts.
However, if it uses the table with the many records it still keeps trying to connect to other hosts forever, throwing exceptions. If I switch it to a clean table it runs without exceptions.
Is there any way to resolve this without clearing the table?
Any insight on my question above? This issue still happens sometimes. Is using localhost clustering the only option here?
This should work. One change which might be needed is to set listenOnAllHostAddresses: true
. I have opened a PR to update docs with full instructions: https://github.com/dotnet/docs/pull/42781/files#diff-b66d9de75a966a6e75cbc3d3608c153dac5340e7d12a2ef6ba6758929e2875b9
We have an Azure App Service running Orleans 7.2.4 with ASP.NET Core on .NET 8. It has been running well for a few weeks. This morning after a scheduled upscale the site failed to start and logs exceptions like this:
These happened continuously for hours. We had to remove Orleans before the site would start up.
Private ports are configured to provide 2 ports. Orleans is configured like this:
We also use Orleans Dashboard. We do not use reminders or streams.
The App Service has only 1 instance and is the only member of the cluster. The clustering table has about 100 rows in it. The Status of some rows is Dead but many more are Joining or Active.
Changing to a different clustering table didn't resolve the issue.