From 621ea892a299d2029348db2b56fea1338bd41c48 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Tue, 31 Jan 2017 12:13:29 -0500 Subject: 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/pacemaker/database/mysql.pp | 1 + 1 file changed, 1 insertion(+) (limited to 'manifests/profile/pacemaker/database') diff --git a/manifests/profile/pacemaker/database/mysql.pp b/manifests/profile/pacemaker/database/mysql.pp index 6a83f10..ca9a1a8 100644 --- a/manifests/profile/pacemaker/database/mysql.pp +++ b/manifests/profile/pacemaker/database/mysql.pp @@ -75,6 +75,7 @@ class tripleo::profile::pacemaker::database::mysql ( 'default-storage-engine' => 'innodb', 'innodb_autoinc_lock_mode' => '2', 'innodb_locks_unsafe_for_binlog'=> '1', + 'innodb_file_per_table' => 'ON', 'query_cache_size' => '0', 'query_cache_type' => '0', 'bind-address' => $bind_address, -- cgit 1.2.3-korg