From 1d0f39ee72113414b216636f755edecdca9b668a Mon Sep 17 00:00:00 2001 From: Marcus Furlong Date: Thu, 21 Jun 2018 18:59:17 +0000 Subject: [PATCH] ha-guide: fix incorrect statement about innodb_flush_log_at_trx_commit It looks like there was a typo for the values of innodb_flush_log_at_trx_commit Per http://galeracluster.com/documentation-webpages/configuration.html Note Warning: While setting innodb_flush_log_at_trx_commit to a value of 0 or 2 improves performance, it also introduces certain dangers. Operating system crashes or power outages can erase the last second of transaction. Although normally you can recover this data from another node, it can still be lost entirely in the event that the cluster goes down at the same time, (for instance, in the event of a data center power outage). Change-Id: I09d0e0be4c85e6bd5469a35482a6392491168298 --- doc/ha-guide/source/shared-database-configure.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ha-guide/source/shared-database-configure.rst b/doc/ha-guide/source/shared-database-configure.rst index 1efde1627a..808b5576fc 100644 --- a/doc/ha-guide/source/shared-database-configure.rst +++ b/doc/ha-guide/source/shared-database-configure.rst @@ -211,7 +211,7 @@ parameters that you must define to avoid conflicts. innodb_flush_log_at_trx_commit=0 - Setting this parameter to ``1`` or ``2`` can improve + Setting this parameter to ``0`` or ``2`` can improve performance, but it introduces certain dangers. Operating system failures can erase the last second of transactions. While you can recover this data from another node, if the cluster goes down at the same time