From 062a64dc09ffadfa4dd414b10b48fa81bacc294e Mon Sep 17 00:00:00 2001 From: rajat29 Date: Thu, 10 Aug 2017 11:49:55 +0530 Subject: [PATCH] Wrong option mentioned to be used by HAproxy with Galera It's mentioned opention "STACK-TABLE" should be used in the configuration file of HAproxy with Galera, it should be "STICK-TABLE" Change-Id: Ia8e2b05be3f7b842794529da469e46761f715a07 Closes-Bug:#1709198 --- doc/ha-guide/source/intro-ha-arch-pacemaker.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ha-guide/source/intro-ha-arch-pacemaker.rst b/doc/ha-guide/source/intro-ha-arch-pacemaker.rst index f00e00a350..afa231cbb8 100644 --- a/doc/ha-guide/source/intro-ha-arch-pacemaker.rst +++ b/doc/ha-guide/source/intro-ha-arch-pacemaker.rst @@ -182,7 +182,7 @@ We recommend HAProxy as the load balancer, however, there are many alternative load balancing solutions in the marketplace. Generally, we use round-robin to distribute load amongst instances of -active/active services. Alternatively, Galera uses ``stack-table`` options +active/active services. Alternatively, Galera uses ``stick-table`` options to ensure that incoming connection to virtual IP (VIP) are directed to only one of the available back ends. This helps avoid lock contention and prevent deadlocks, although Galera can run active/active. Used in combination with