diff options
| author |   Alex Schultz <aschultz@redhat.com> | 2017-02-03 18:18:42 +0000 |
|---|---|---|
| committer | Alex Schultz <aschultz@redhat.com> | 2017-02-03 19:50:08 +0000 |
| commit | a0983a4ed743e9d0ca152c29303cce73a1ca5113 (patch) | |
| tree | d6a11a7737e45124e7ff422525ddd1cd5d8e04a7 /releasenotes/notes | |
| parent | 3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e (diff) | |
Revert "Revert "set innodb_file_per_table to ON for MySQL / Galera""
This reverts commit 3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e.
After identifying how to workaround the performance issues on the
undercloud, let's put this back in. Enabling innodb_file_per_table is
important for operators to be able to better manage their databases.
Change-Id: I435de381a0f0e3ef221e498f442335cdce3fb818
Depends-On: I77507c638237072e38d9888aff3da884aeff0b59
Closes-Bug: #1660722
Diffstat (limited to 'releasenotes/notes')
| -rw-r--r-- | releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml | 20 |
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 @@ +--- +features: + - Enable innodb_file_per_table for MySQL/MariaDB databases +upgrade: + - | + 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. |