Code Review / apex-puppet-tripleo.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 875a9f9) | patch
set innodb_file_per_table to ON for MySQL / Galera
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 31 Jan 2017 17:13:29 +0000 (12:13 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 1 Feb 2017 21:12:13 +0000 (16:12 -0500)
commit621ea892a299d2029348db2b56fea1338bd41c48
treeb40d9f7ae4cfc59a4cf35ff64efbfc389017a8d0tree | snapshot
parent875a9f90157f235334cd224d84fecc3d5c3cc814commit | diff
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
manifests/profile/base/database/mysql.pp diff | blob | history
manifests/profile/pacemaker/database/mysql.pp diff | blob | history
releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml [new file with mode: 0644] blob