Document updated on Sep 27, 2018
Having a high number of IDLE connections to every backend affects directly to the performance of the proxy layer. This is why you can control the number using the max_idle_connections
setting. For instance:
{
"version": 2,
"max_idle_connections": 150,
...
}
KrakenD will close connections sitting idle in a “keep-alive” state when max_idle_connections
is reached. If no value is set in the configuration file, KrakenD will use 250
by default.
Every ecosystem needs its own setting, have this in mind:
max_idle_connections
you might exhaust your system’s port limit.For more information on the transport layer, see MaxIdleConnsPerHost
The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.
We use cookies to understand how you use our site and to improve your overall experience. By continuing to use our site, you accept our Privacy Policy. More information