path: root/releasenotes
diff options
authorAlex Schultz <aschultz@redhat.com>2017-02-02 21:29:32 +0000
committerAlex Schultz <aschultz@redhat.com>2017-02-02 21:43:41 +0000
commit3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e (patch)
treeb8b6e692c5203377eddc327473d092cdd3b61493 /releasenotes
parentda0e9fdf5a8b33b5b92627bde35d76c7fdbb1b55 (diff)
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
Diffstat (limited to 'releasenotes')
1 files changed, 0 insertions, 20 deletions
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 @@
- - 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.