Hi Marko,
Thanks for the heads up,
In fact "log-balance" directive was removed in
> commit b61147fd2a54d4cfc1053a51e87c91cc306bb7ed
> Author: Aurelien DARRAGON <adarra...@haproxy.com>
> Date: Wed Nov 15 11:15:50 2023 +0100
>
> MEDIUM: log/balance: merge tcp/http algo with log ones
log load balancing may now be configured using the existing "balance"
directive for log backends as explained in the haproxy-2.9-dev10 release
note.
However I forgot to remove the "log-balance" keyword from the proxy
keyword matrix, which could explain why you thought the documentation
was missing. My bad!
Here is a complementary patch to
b61147fd2a54d4cfc1053a51e87c91cc306bb7ed to remove the documentation
leftovers for "log-balance" directive which doesn't exist anymore in the
code.
Aurelien
From 8e675f826498c5c6d8067d5a77427ee13423d89b Mon Sep 17 00:00:00 2001
From: Aurelien DARRAGON <adarra...@haproxy.com>
Date: Tue, 21 Nov 2023 11:28:26 +0100
Subject: [PATCH] DOC: config: removing "log-balance" references
"log-balance" keyword was removed by b61147f ("MEDIUM: log/balance: merge
tcp/http algo with log ones") but it was still documented.
Removing "log-balance" references in the documentation where needed.
---
doc/configuration.txt | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index c2f30a944..414bfdc6f 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -4500,7 +4500,6 @@ id - X X X
ignore-persist - - X X
load-server-state-from-file X - X X
log (*) X X X X
-log-balance X - X X
log-format X X X -
log-format-sd X X X -
log-tag X X X X
@@ -9115,10 +9114,9 @@ mode { tcp|http|log }
any "log" directive by using the "backend@<name>" syntax. Log
messages will be distributed to the servers from the backend
according to the lb settings which can be configured using the
- "log-balance" keyword (in place of the "balance" keyword for TCP
- and HTTP backends). Log backends support UDP servers by prefixing
+ "balance" keyword. Log backends support UDP servers by prefixing
the server's address with the "udp@" prefix. Common backend and
- server features are supported, but not TCP or HTTP related ones.
+ server features are supported, but not TCP or HTTP specific ones.
When doing content switching, it is mandatory that the frontend and the
backend are in the same mode (generally HTTP), otherwise the configuration
--
2.34.1
