Connection Drop every day without apparent code reason

[kauezatarinpecege]

Describe the bug

Hello!

I’m involved into an investigation about signalR users being disconnected every
day, generally at the same timespan. I really can’t see queer the problem is, and
everything points to a SignalR hub issue (as if the hub has been reopening
some connections randomly).

Our SignalR hubs are hosted on an Azure App Service, and the backend SDK
version is 1.30.1 (8.0.7 on frontend).

As you can see in the below charts, we have a connectionCount drop at
many subsequent days. I’ve checked on the server side and nothing really
happened at this timespan. Virtually there is no reason to so many connections
to be interrupted at once.

When the problem first started the last application release (front and back) had been made two months ago.

We have a reconnection logic on the clients, so they will reconnect right after.
The major problem here is that all the clients try to reconnect in a short period of time, and it
makes the backend reach 100% CPU usage very quickly wich leads to a service downtime.

This is really weird, also. Can somebody explain why there are so many
ServiceReloads at this time?

Did anybody experienced something like this before? Am I missing something?
Any help is appreciated!

To Reproduce

We are not sure on how to reproduce this error as it seems to be related to the events mentioned above.

We will close this issue if:

• we understand what is causing the connections drop

Further technical details

• Azure SignalR SDK version - 1.30.1
• SignalR Client SDK version - 8.0.7

[vicancy]

Thanks for reporting the issue. We've identified an infra layer configuration change that could trigger a regional reload. Recently such infra layer change becomes more frequent. We are applying a hotfix to all regions to mitigate the issue.

What is the region of your resource?

[kauezatarinpecege]

Hello @vicancy , Thanks for your reply.

Our infra is located at East US location. Do you know when this hotfix will be applied to my region?
Another piece of information that might help, last year we experienced a similar issue with the service (#1853) during the same quarter. Do you think this might be related?