From a5117191f9bdc04fdfff271aa2d5593f803756d4 Mon Sep 17 00:00:00 2001 From: Michael Coburn Date: Tue, 15 Dec 2020 09:27:34 -0600 Subject: [PATCH 1/3] Update certification.rst making the update action: more clear with the variable trx_id --- doc/source/manual/certification.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/manual/certification.rst b/doc/source/manual/certification.rst index d926cbf07f98..81758b4c2465 100644 --- a/doc/source/manual/certification.rst +++ b/doc/source/manual/certification.rst @@ -131,8 +131,8 @@ The following happens if two nodes get ready with their packet at same time: Although the real algorithm is more involved (with ``uuid`` + ``seqno``), it is conceptually the same, so we are using ``trx_id``. - * Node 1: ``update action: trx-id=n1x`` - * Node 2: ``update action: trx-id=n2x`` + * Node 1: ``update action: trx_id=n1x`` + * Node 2: ``update action: trx_id=n2x`` Both node packets are added to the channel, but the transactions are conflicting. From 9de1677f850f992160483e2dc8933cea01c27cf4 Mon Sep 17 00:00:00 2001 From: Michael Coburn Date: Tue, 15 Dec 2020 09:32:11 -0600 Subject: [PATCH 2/3] trx-id -> trx_id making the update action: more clear with the variable trx_id --- doc/source/manual/certification.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/manual/certification.rst b/doc/source/manual/certification.rst index 81758b4c2465..a8b5491079e0 100644 --- a/doc/source/manual/certification.rst +++ b/doc/source/manual/certification.rst @@ -126,7 +126,7 @@ The following happens if two nodes get ready with their packet at same time: * Node 1: ``update i = i + 10;`` * Node 2: ``update i = i + 100;`` - Let's associate transaction ID (``trx-id``) for an update transaction + Let's associate transaction ID (``trx_id``) for an update transaction that is executed on Node 1 and Node 2 in parallel. Although the real algorithm is more involved (with ``uuid`` + ``seqno``), it is conceptually the same, so we are using ``trx_id``. From 9c0ce4b2b5febfc45a10fe817345aa52a2420fe3 Mon Sep 17 00:00:00 2001 From: Michael Coburn Date: Fri, 24 Jun 2022 16:39:56 -0500 Subject: [PATCH 3/3] add socket.ssl=yes directive Seems to be required now in 8.0.27 --- doc/source/howtos/garbd_howto.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/source/howtos/garbd_howto.rst b/doc/source/howtos/garbd_howto.rst index b43ac6a40414..b9d9e959d1db 100644 --- a/doc/source/howtos/garbd_howto.rst +++ b/doc/source/howtos/garbd_howto.rst @@ -54,7 +54,8 @@ When starting from the shell, you can set the parameters from the command line o --option="socket.ssl_key=/etc/ssl/mysql/server-key.pem; \ socket.ssl_cert=/etc/ssl/mysql/server-cert.pem; \ socket.ssl_ca=/etc/ssl/mysql/ca.pem; \ - socket.ssl_cipher=AES128-SHA256" + socket.ssl_cipher=AES128-SHA256; \ + socket.ssl=yes" To avoid entering the options each time you start ``garbd``, edit the options in the configuration file. To configure *Galera Arbitrator* on *Ubuntu/Debian*, edit the :file:`/etc/default/garb` file. On RedHat or derivative distributions, the configuration can be found in :file:`/etc/sysconfig/garb` file.