Closed StevenBarre closed 11 months ago
KLAB Before HAProxy Stats
CLAB Before HAProxy Stats
KLAB After HAProxy Stats
CLAB After HAProxy Stats
No issues in the past week with the new settings. Memory usage appears to be a little lower as well. Should be safe to move into production.
CHG0054991 scheduled for Jan 3rd
Slide added to next community meetup
Describe the issue HAProxy on Silver currently uses a lot of memory, and drives a high load average on the Infra nodes. There are some tuning options available.
HAProxy reloads the config up to every 5 seconds as changes in routes happen. This can be due to pods changing from Ready to Non-Ready or new pods being scaled up.
Each time HAProxy reloads, a new process is spawned and the old process remains open until all connections it is handling have exited. However, with websockets and other long running connections that use keepalive, these connections may be open for weeks at a time.
What is the Value/Impact? Improved infra node stability
What is the plan? How will this get completed? In the labs, test out the two tuning configs.
1) Edit the
ingresses.config/cluster
to add thehard-stop-after
annotation. This will set the max lifetime of long lived connections like websockets. Starting point may be 6h2) Edit the default ingresscontroller to set the reload time to a value higher than 5s so that less haproxy processes are spawned.
Identify any dependencies None
Definition of done