When the Portal is running with a single instance the SignalR can keep the connection normally because just there 1 node, but when the Portal is running in with multiple instances there is a problem with SignalR because we have more than one node. So a single instance of the portal works fine, but multiple instances of the portal do not work correctly, the chat feature becomes unresponsive as connections are being dropped.
Connections to SignalR start to drop as you can see in this screen shot. Scroll down to see the errors.
[attachment=0:1e5qwp3r]SignalR_Issue_Cropped.png[/attachment:1e5qwp3r]
1 Answer(s)
-
0
Hi,
You need to scale-out SignalR. Default version is not suitable for scale-out environment. I couldn't find a documentation for ASP.NET Core SignalR but there are some issues on GitHub related to this. You can check this one <a class="postlink" href="https://github.com/aspnet/SignalR/issues/991">https://github.com/aspnet/SignalR/issues/991</a>.
