path: root/releasenotes
diff options
authorJenkins <jenkins@review.openstack.org>2017-07-17 08:20:11 +0000
committerGerrit Code Review <review@openstack.org>2017-07-17 08:20:11 +0000
commit1b4effb7fde1bd330e3f59bcab8c7a7efd649d06 (patch)
tree11e503ec13516119bcf7cd8b66aaf6fef7cf02ae /releasenotes
parent483239a62539d772ddc18bd0b2b106efd0271200 (diff)
parent8b2d4047774ead6223adf2b98e30b9e6ca9ca3d2 (diff)
Merge "Add option for innodb_flush_log_at_trx_commit = 2 for Galera only"
Diffstat (limited to 'releasenotes')
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 @@
+ - |
+ Enable innodb_flush_log_at_trx_commit configuration for Galera only.
+ - |
+ 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.