3 Commits

Author SHA1 Message Date
Alex Schultz
a0983a4ed7 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
2017-02-03 19:50:08 +00:00
Alex Schultz
3f7e74ab24 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
2017-02-02 21:43:41 +00:00
Mike Bayer
621ea892a2 set innodb_file_per_table to ON for MySQL / Galera
InnoDB uses a single file by default which can grow to be
tens/hundreds of gigabytes, and is not shrinkable even
if data is deleted from the database.

Best practices are that innodb_file_per_table is set to ON
which instead stores each database table in its own file, each of
which is also shrinkable by the InnoDB engine.

Closes-Bug: #1660722
Change-Id: I59ee53f6462a2eeddad72b1d75c77a69322d5de4
2017-02-01 16:12:13 -05:00