daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improve session affinity remarks (#33719)

pull/33721/head
Luke Latham 2024-09-26 06:22:21 -04:00 committed by GitHub
parent 211cf9eec4
commit 04e07a1d1b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/blazor/fundamentals/signalr.md
View File

@ -181,7 +181,7 @@ To resolve the problem, use ***either*** of the following approaches:
## Use session affinity (sticky sessions) for server-side webfarm hosting
A Blazor app prerenders in response to the first client request, which creates UI state on the server. When the client attempts to create a SignalR connection, the client must reconnect to the same server. When more than one backend server is in use, the app should implement session affinity, also called *sticky sessions*, for SignalR connections.
When more than one backend server is in use, the app must implement session affinity, also called *sticky sessions*. Session affinity ensures that a client's circuit reconnects to the same server if the connection is dropped, which is important because client state is only held in the memory of the server that first established the client's circuit.
The following error is thrown by an app that hasn't enabled session affinity in a webfarm: