path: root/releasenotes
diff options
authorJenkins <jenkins@review.openstack.org>2017-02-06 01:41:40 +0000
committerGerrit Code Review <review@openstack.org>2017-02-06 01:41:40 +0000
commit2b11f29824719f961d35c66617f3ee654cf9f0f3 (patch)
treea6b9933cf9a0e8fd7b206fa46f13be226be7c4de /releasenotes
parenta75c6c618e34d74389b9963f994f5e18ec29674a (diff)
parenta0983a4ed743e9d0ca152c29303cce73a1ca5113 (diff)
Merge "Revert "Revert "set innodb_file_per_table to ON for MySQL / Galera"""
Diffstat (limited to 'releasenotes')
1 files changed, 20 insertions, 0 deletions
diff --git a/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml b/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml
new file mode 100644
index 0000000..e0b7c3c
--- /dev/null
+++ b/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml
@@ -0,0 +1,20 @@
+ - Enable innodb_file_per_table for MySQL/MariaDB databases
+ - |
+ Newly created MySQL database tables will be stored in their own datafiles,
+ instead of in a single monolithic ibdata file.
+ - |
+ Existing MySQL database tables that are persisted within the monolithic
+ ibdata file will remain so unless the database is migrated as well.
+ - |
+ Migration of all current database tables out of the monolithic ibdata
+ file is possible by dumping and restoring the whole database to a new data
+ directory, however when using Galera the entire cluster must be shut
+ down and upgraded at once.
+ - |
+ Migration of individual tables to datafiles is possible using the
+ MySQL command "ALTER TABLE <databasename>.<tablename> ENGINE=InnoDB;",
+ however this will not shrink the ibdata file and also is not safe to run
+ on a running Galera cluster for large tables.