We have 4 servers, with a load balancer (AWS ALB) in front. Meteor requires sticky sessions so ALB is configured to use that.
Today one of the servers had a cpu spike and stopped responding. Even when we manually restarted it, all the clients on it were getting 502 (because they were being sent to its ip).
Is there any way to handle this in Meteor since its not stateless? This is needless to say a very bad user experience.