mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
27 lines
1.5 KiB
Plaintext
27 lines
1.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * scalability_and_performance/optimization/routing-optimization.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="configuring-haproxy-interval_{context}"]
|
|
= Configuring HAProxy reload interval
|
|
|
|
When you update a route or an endpoint associated with a route, the {product-title} router updates the configuration for HAProxy. Then, HAProxy reloads the updated configuration for those changes to take effect. When HAProxy reloads, it generates a new process that handles new connections using the updated configuration.
|
|
|
|
HAProxy keeps the old process running to handle existing connections until those connections are all closed. When old processes have long-lived connections, these processes can accumulate and consume resources.
|
|
|
|
The default minimum HAProxy reload interval is five seconds. You can configure an Ingress Controller using its `spec.tuningOptions.reloadInterval` field to set a longer minimum reload interval.
|
|
|
|
[WARNING]
|
|
====
|
|
Setting a large value for the minimum HAProxy reload interval can cause latency in observing updates to routes and their endpoints. To lessen the risk, avoid setting a value larger than the tolerable latency for updates.
|
|
====
|
|
|
|
.Procedure
|
|
|
|
* Change the minimum HAProxy reload interval of the default Ingress Controller to 15 seconds by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n openshift-ingress-operator patch ingresscontrollers/default --type=merge --patch='{"spec":{"tuningOptions":{"reloadInterval":"15s"}}}'
|
|
----
|