MySQL is not configured with innodb_file_per_table = 1

Bug #1316003 reported by Richard Kiene
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
Undecided
Unassigned

Bug Description

In Fuel 4.0 MySQL should be configured to use innodb_file_per_table = 1: https://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_file_per_table

In only a few months time our Keystone database has grown to 30+ GB of tokens (which should probably be a separate bug, that a cron job isn't setup to deal with that).

If innodb_file_per_table was enabled I could simply delete expired tokens, backup the keystone database, drop or truncate the token table and I would free up nearly 30GB of wasted space.

Because innodb_file_per_table is disabled I have to delete expired tokens, take everything offline, backup all database in the cluster, delete ibdata1, ib_log, etc. and restore every schema from backup before bringing the server back online, just to free up wasted tokens.

Given that just a few months in a modest sized private install can result in 30GB of expired keystone tokens, file per table should be enabled so that it is easier to clear up unnecessarily used space.

summary: - MySQL ibdata1 grows out of control because Fuel does not configure MySQL
- to use innodb_file_per_table
+ MySQL is not configured to use innodb_file_per_table
summary: - MySQL is not configured to use innodb_file_per_table
+ MySQL is not configured with innodb_file_per_table = 1
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Richard, please provide which version of FUEL this bug is related to. We fixed this issue a long time ago.

Changed in fuel:
status: New → Incomplete
Revision history for this message
Richard Kiene (richard-kiene) wrote :

Vladimir, this is in Fuel 4.0.

Changed in fuel:
status: Incomplete → New
description: updated
Revision history for this message
Richard Kiene (richard-kiene) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.