You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In single connection mode, the client makes two requests to establish a connection:
The first request pushes a connection ID.
The second request uses that ID to establish the connection.
However, I noticed an issue when the server is running multiple processes or containers under a load balancer. Since there is no guarantee that both requests will hit the same instance, and the current implementation does not support shared memory, how can this be addressed?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In single connection mode, the client makes two requests to establish a connection:
However, I noticed an issue when the server is running multiple processes or containers under a load balancer. Since there is no guarantee that both requests will hit the same instance, and the current implementation does not support shared memory, how can this be addressed?
Beta Was this translation helpful? Give feedback.
All reactions