DOC: nbthread is no longer experimental.

It was mentioned when releasing 1.8 but early bugs have long been
addressed and this comment discourages some users from using threads.

This should be backported to 1.9 and 1.8 now.
This commit is contained in:
Willy Tarreau 2019-01-26 14:20:55 +01:00
parent f5809cde7a
commit 1f672a8162

View File

@ -958,14 +958,14 @@ nbproc <number>
mode. By default, only one process is created, which is the recommended mode mode. By default, only one process is created, which is the recommended mode
of operation. For systems limited to small sets of file descriptors per of operation. For systems limited to small sets of file descriptors per
process, it may be needed to fork multiple daemons. USING MULTIPLE PROCESSES process, it may be needed to fork multiple daemons. USING MULTIPLE PROCESSES
IS HARDER TO DEBUG AND IS REALLY DISCOURAGED. See also "daemon". IS HARDER TO DEBUG AND IS REALLY DISCOURAGED. See also "daemon" and
"nbthread".
nbthread <number> nbthread <number>
This setting is only available when support for threads was built in. It This setting is only available when support for threads was built in. It
creates <number> threads for each created processes. It means if HAProxy is creates <number> threads for each created processes. It means if HAProxy is
started in foreground, it only creates <number> threads for the first started in foreground, it only creates <number> threads for the first
process. FOR NOW, THREADS SUPPORT IN HAPROXY IS HIGHLY EXPERIMENTAL AND IT process. See also "nbproc".
MUST BE ENABLED WITH CAUTION AND AT YOUR OWN RISK. See also "nbproc".
pidfile <pidfile> pidfile <pidfile>
Writes PIDs of all daemons into file <pidfile>. This option is equivalent to Writes PIDs of all daemons into file <pidfile>. This option is equivalent to