a0983a4ed7
This reverts commit 3f7e74ab24.
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
21 lines
915 B
YAML
21 lines
915 B
YAML
---
|
|
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.
|