Bug #72633 --skip-innodb option ignored in 5.7 servers
Submitted: 13 May 2014 16:49 Modified: 5 Sep 2014 5:26
Reporter: Nelson Goncalves Email Updates:
Status: Closed Impact on me:
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:1.4.3 OS:Any
Assigned to: CPU Architecture:Any

[13 May 2014 16:49] Nelson Goncalves
The --skip-innodb option is ignored in 5.7 version of the server.

This option is used in the _start_server function in the serverinfo file to start a server in read_only mode 
with the innodb engine disabled. However with the 5.7 version of the server we will be unable to disable innodb since that option is removed
and its use will be ignored. 

How to repeat:
Run the serve_info test on mut with 5.7 server as the base server.

Suggested fix:
Issue a warning stating that we are unable to disable innnodb engine
in case the server version is 5.7.  Furthermore the current code that
adds the --skip-innodb option only does that if the server is version
5.6 or above.  This is not correct since innodb engine is also the
default engine in 5.5 and can also be disabled. The current code needs
to take that into account.  According to the manual, in the 5.5
version the "--skip-innodb" option needs to used together with the
"--default-storage-engine" and for 5.6 servers the "--skip-innodb"
option needs to used in conjunction with both
"--default-storage-engine" and "--default-tmp-storage-engine"
otherwise the server won't start.
[5 Sep 2014 5:26] Philip Olson
Fixed as of the upcoming MySQL Utilities 1.5.2 release, and here's the changelog entry:

The "--skip-innodb" option is used by the utilities, but this option is
ignored in MySQL 5.7+. A warning is now issued for this scenario.

Thank you for the bug report.