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
Long lived HTTP connections can cause load imbalance on a pool of backend servers. If the servers are autoscaling the load wont be equally distributed to new instances of the backend server. It would be helpful to be able to configure a max connection life time that is enforced by the ember server that closes the connection on the server side after a configurable period of time.
This issue is related to #3700 but focuses on the server side.
Tomcat has a keepAliveTimeout which I think is the same as this.
Long lived HTTP connections can cause load imbalance on a pool of backend servers. If the servers are autoscaling the load wont be equally distributed to new instances of the backend server. It would be helpful to be able to configure a max connection life time that is enforced by the ember server that closes the connection on the server side after a configurable period of time.
This issue is related to #3700 but focuses on the server side.
Tomcat has a keepAliveTimeout which I think is the same as this.
Armeria Server has similar functionality added in line/armeria#2747
The text was updated successfully, but these errors were encountered: