-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global downstream connection limits. #1966
Comments
It appears that the functionality is incomplete and unsuitable for production use. Should we enable it? |
@tmsnan im fine waiting, but atm we dont have any way of enabling overload manager |
@arkodg If possible, I could first add other overload manager features that are already fully supported. |
@tmsnan sure, imo the others like heap size based will require an API addition, putting the burden of getting it right on the user . |
@arkodg Maybe we can refer to Google VRP edge server configuration.
https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge
Gateway will use overloadmanage (passing envoy configuration similar to Google VRP edge server configuration) when configuring overloadManager's MaxHeapSizeBytes, otherwise it will not be enabled. Is this method OK? |
yes this is the one I was referring to, which will require an API change, but we need to have a simple recommendation for the user for a value to set in this API. e.g. |
suggest using the value from best practices doc
|
Please assign me |
Add a overload manager configuration to limit the total number of downstream connections
https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/overload_manager/overload_manager#limiting-active-connections
The text was updated successfully, but these errors were encountered: