File: imtcp-socketbacklog.rst

package info (click to toggle)
rsyslog 8.2512.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 30,464 kB
  • sloc: ansic: 123,809; sh: 42,109; makefile: 5,962; javascript: 1,842; python: 1,222; lex: 607; yacc: 193; perl: 162; sql: 103; tcl: 9; ruby: 2
file content (61 lines) | stat: -rw-r--r-- 1,896 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
.. _param-imtcp-socketbacklog:
.. _imtcp.parameter.input.socketbacklog:

SocketBacklog
=============

.. index::
   single: imtcp; SocketBacklog
   single: SocketBacklog

.. summary-start

Sets the backlog length for pending TCP connections.

.. summary-end

This parameter applies to :doc:`../../configuration/modules/imtcp`.

:Name: SocketBacklog
:Scope: input
:Type: integer
:Default: input=10% of configured connections
:Required?: no
:Introduced: 8.2502.0

Description
-----------
Specifies the backlog parameter passed to the ``listen()`` system call. This parameter defines the
maximum length of the queue for pending connections, which includes partially established connections
(those in the SYN-ACK handshake phase) and fully established connections waiting to be accepted by the
application.

**Available starting with the 8.2502.0 series.**

For more details, refer to the ``listen(2)`` man page.

By default, the value is set to 10% of the configured connections to accommodate modern workloads. It
can be adjusted to suit specific requirements, such as:

- **High rates of concurrent connection attempts**: Increasing this value helps handle bursts of
  incoming connections without dropping them.
- **Test environments with connection flooding**: Larger values are recommended to prevent SYN queue
  overflow.
- **Servers with low traffic**: Lower values may be used to reduce memory usage.

The effective backlog size is influenced by system-wide kernel settings, particularly
``net.core.somaxconn`` and ``net.ipv4.tcp_max_syn_backlog``. The smaller value between this parameter
and the kernel limits is used as the actual backlog.

Input usage
-----------
.. _param-imtcp-input-socketbacklog:
.. _imtcp.parameter.input.socketbacklog-usage:

.. code-block:: rsyslog

   input(type="imtcp" socketBacklog="128")

See also
--------
See also :doc:`../../configuration/modules/imtcp`.