Skip to content

Optimizations for HAProxy reloads #6744

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Dec 13, 2017
Merged

Optimizations for HAProxy reloads #6744

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions scaling_performance/routing_optimization.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,3 +125,18 @@ accepted by load balancers provided by many public cloud providers. However,
this affects the total memory use, especially when large numbers of connections
are open. With very large numbers of open connections, the memory usage will be
nearly proportionate to the increase of this tunable parameter.

[[optimizations-for-haproxy-reloads]]
==== Optimizations for HAProxy Reloads

Long-lasting connections, such as WebSocket connections, combined with
long client/server HAProxy timeouts and short HAProxy
reload intervals, can cause instantiation of many HAProxy processes.
These processes must handle old connections, which were started
before the HAProxy configuration reload. A large number of these processes is
undesirable, as it will exert unnecessary load on the system and can
lead to issues, such as out of memory conditions.

xref:../architecture/topics/router_environment_variables.adoc#[Router environment variables] affecting this
behavior are `ROUTER_DEFAULT_TUNNEL_TIMEOUT`, `ROUTER_DEFAULT_CLIENT_TIMEOUT`,
`ROUTER_DEFAULT_SERVER_TIMEOUT`, and `RELOAD_INTERVAL` in particular.