Merge "Add option for innodb_flush_log_at_trx_commit = 2 for Galera only"

1 files changed, 17 insertions, 0 deletions

diff --git a/releasenotes/notes/innodb_flush_log_at_trx_commit-eb7d99749ca3c911.yaml b/releasenotes/notes/innodb_flush_log_at_trx_commit-eb7d99749ca3c911.yaml
new file mode 100644
index 0000000..7dbd5a7
--- /dev/null
+++ b/releasenotes/notes/innodb_flush_log_at_trx_commit-eb7d99749ca3c911.yaml
@@ -0,0 +1,17 @@
+---
+features:
+  - |
+    Enable innodb_flush_log_at_trx_commit configuration for Galera only.
+upgrade:
+  - |
+    Setting the innodb_flush_log_at_trx_commit flag to the value of "2" instead
+    of its default value of "1" means that the underlying MySQL/MariaDB engine
+    will no longer flush transactions to disk on a per-transaction basis;
+    instead, flushes occur once per second.   This leads to far fewer
+    disk writes and can dramatically improve write performance, at the cost
+    of durability (e.g. will lose the last second's worth of transactions)
+    if the database engine is ungracefully shut down.   The
+    clustered nature of Galera mitigates this risk in that transactions
+    are replicated to other nodes before completion, and the setting of
+    "2" is considered to be generally safe for a Galera cluster, with the
+    exception case of simultaneous power loss for all nodes.