Bug #42096 MEM my.cnf innodb_autoextend_increment 50M invalid
Submitted: 14 Jan 2009 0:19 Modified: 3 Mar 2009 15:07
Reporter: Adam Dixon Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:2.0.7125 OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[14 Jan 2009 0:19] Adam Dixon 
Description:
The my.cnf for the internal Enterprise Monitor database has the following configuration set;
innodb_autoextend_increment = 50M

This should actually be;
innodb_autoextend_increment = 50

as this variable is read-in as megabytes (50M would be 50+ million megabytes which is surely not intended and errors back out to 1000);

16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800
adjusted to 1000

How to repeat:
Install Enterprise monitor.

Suggested fix:
Change my.cnf to 50 instead of 50M
[14 Jan 2009 0:19] Adam Dixon 
http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#option_mysqld_innodb_autoext...
[14 Jan 2009 15:01] Mark Leith 
This should be removed, along with the 500M setting for the ibdata file - as we now use innodb_file_per_table as well.
[14 Jan 2009 19:13] Gary Whizin 

 

 

  

   [14 Jan 2009 23:12]
   Andy Bang        

  
Fixed in 2.0:

Committed revision 775.

QA: The fix also needs to be applied to 2.0.  After you verify the fix, please put the bug back in Verified with a Target Version of "2.1".

 

 

  

   [28 Jan 2009 23:28]
   Andy Bang        

  
QA: Also now fixed in 2.1:

Committed revision 793.

So please test in both builds and do not set back to Verified unless it's not fixed in both places.

 

 

  

   [4 Feb 2009 23:22]
   Keith Russell        

  
Patch installed in versions => 2.0.5.7144.

 

 

  

   [4 Feb 2009 23:28]
   Keith Russell        

  
Status updated by mistake.

 

 

  

   [26 Feb 2009 0:04]
   Keith Russell        

  
Patch installed in versions => 2.1.0.1011.

 

 

  

   [2 Mar 2009 17:34]
   Bill Weber        

  
verified this has been removed in both 2.0.5.7148 and 2.1.0.1011

 

 

  

   [3 Mar 2009 15:07]
   Tony Bedford        

  
Entries have been added to the 2.0.5 and 2.1.0 changelogs:

The my.cnf file for the Enterprise Monitor internal database had the following configuration item:

innodb_autoextend_increment = 50M

This generated the error:

16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800
adjusted to 1000

This variable is interpreted as being specified in MB, so 50M would be 50 TB. Such a high value results in the variable being adjusted to 1000 MB.

The value in the configuration file should be:

innodb_autoextend_increment = 50