Bug #74835 | Embedded server fails to bootstrap/start up with innodb_undo_tablespaces=2 | ||
---|---|---|---|
Submitted: | 13 Nov 2014 9:34 | Modified: | 5 May 2015 15:52 |
Reporter: | Marko Mäkelä | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.7.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[13 Nov 2014 9:34]
Marko Mäkelä
[5 May 2015 15:52]
Daniel Price
Fixed as of the upcoming 5.7.8, 5.8.0 releases, and here's the changelog entry: An embedded MySQL server failed to start with "innodb_undo_tablespaces=2". The server was unable to locate undo tablespaces that were created when the MySQL instance was initialized. For embedded MySQL installations, the "innodb_undo_directory" default value of ""."" may not be the same directory as the MySQL data directory. To address this problem, "innodb_undo_directory" is now NULL by default, requiring that a path be specified. If a path is not specified, undo tablespaces are created in the MySQL data directory, as defined by "datadir". A workaround for pre-MySQL 5.7.8 embedded installations is to define an absolute path for "innodb_undo_directory". Related reference manual updates (changes should appear within the next 24 hours): http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_un do_directory http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_un do_directory http://dev.mysql.com/doc/refman/5.6/en/innodb-undo-tablespace.html http://dev.mysql.com/doc/refman/5.7/en/innodb-undo-tablespace.html