Bug #41967 my.cnf sets large size for central tablespace, but uses innodb_file_per_table
Submitted: 8 Jan 2009 14:41 Modified: 22 May 2009 13:52
Reporter: Mark Leith Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Configuration Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[8 Jan 2009 14:41] Mark Leith
The 2.0 MEM my.cnf uses an initial size of 500M for the central tablespace, however we use innodb_file_per_table as well, so potentially waste ~.5Gb of space. 

How to repeat:

Suggested fix:
This is pretty hard to fix for the upgrade installers now (as we will get an error if we simply adjust it for a running instance).

For full installers we should simply remove the 500M initial size value.
[4 May 2009 23:56] Bill Weber
as per comments in bug, verified this is now supported in 2.1
[22 May 2009 13:52] Tony Bedford
An entry was added to the 2.1.0 changelog:

The MySQL Enterprise Monitor file my.cnf specified an initial size of 500M for the central tablespace. 
However, innodb_file_per_table was used as well, resulting in approximately 500M of space being potentially wasted.