From 3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e Mon Sep 17 00:00:00 2001 From: Alex Schultz Date: Thu, 2 Feb 2017 21:29:32 +0000 Subject: Revert "set innodb_file_per_table to ON for MySQL / Galera" This reverts commit 621ea892a299d2029348db2b56fea1338bd41c48. We're getting performance problems on SATA disks. Change-Id: I30312fd5ca3405694d57e6a4ff98b490de388b92 Closes-Bug: #1661396 Related-Bug: #1660722 --- .../innodb_file_per_table-f925b3bbf29d44ea.yaml | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml (limited to 'releasenotes') diff --git a/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml b/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml deleted file mode 100644 index e0b7c3c..0000000 --- a/releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml +++ /dev/null @@ -1,20 +0,0 @@ ---- -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 . 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. -- cgit 1.2.3-korg