Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
upstream: new property to limit the amount of active TCP connections (#…
…7586) By default, Fluent Bit tries to deliver data as faster as possible and create TCP connections on-demand and in keepalive mode for performance reasons. In high-scalable environments, the user might want to control how many connections are done in parallel by setting a limit. This patch implements a new configuration property called 'net.max_connections' that can be used in the output plugins sections, so Fluent Bit won't open more than net.max_connections if it has been set. If the limit is reached, the output plugins will issue a retry. Configuration example: [OUTPUT] name splunk match * net.max_worker_connections 10 Note that this feature works at upstream/plugin level, and the limit is applied for all the workers if they exists, e.g: if you have 50 workers and net.max_connections=10, only 10 connections will be allowed. --------- Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
- Loading branch information