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.21.7 (7.0.5 on frontend).
As you can see in the below charts, we have a huge 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 a month 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 at once, and it
makes the backend reach 100% CPU usage very quickly.
This is really weird, also. Can somebody explain why there are so many
ServiceReloads at this time?
We have tried to update the SignalR SDKs, creating a new Hub Ressource in a different region.
Did anybody experienced something like this before? Am I missing something?
Any help is appreciated!
If we are not able to address the error/exception for the symptom, I’m afraid we’d better to have a try to address the error/exception first, let’s follow the official document at the beginning. By the way, so many connections dropped at the same time might be a server issue/signalr service issue. If you are using a free pricing tier signalr instance, then you might try to upgrade to S1 tier.