"Session ID unknown" (HTTP 400) during rolling deploys: sticky sessions vs Redis adapter for Socket.IO
I'm planning a zero-downtime migration of a small Socket.IO application to a multi-node setup behind a load balancer. During rolling restarts, clients using the default transports can hit the Engine.IO error Session ID unknown (HTTP 400), because the handshake session lives in memory on the node that issued it and a subsequent polling request may land on a d
nodejs
socketio