Bug #62988 innodb_use_native_aio option does not take ON or OFF as acceptable setting

• Submitted: 28 Oct 2011 1:13
• Modified: 28 Oct 2011 3:15
• Reporter: Dimitriy A
• Status: Duplicate
• Category: MySQL Server: Options
• Severity: S3 (Non-critical)
• Version: 5.5.17
• OS: Linux (64-bit)
• CPU Architecture: Any
• Tags: configuration, innodb_use_native_aio, option, variable

[28 Oct 2011 1:13] Dimitriy A

Description:
In my.cnf, innodb_use_native_aio has been disabled, yet the server is reporting that it is still enabled.
innodb_use_native_aio=OFF

mysql> show variables like 'innodb_use_native_aio';
+-----------------------+-------+
| Variable_name         | Value |
+-----------------------+-------+
| innodb_use_native_aio | ON    |
+-----------------------+-------+

Workaround is to use the following setting instead in my.cnf file:
innodb_use_native_aio=0

In the manual at http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_use_native_aio, ON is listed as default value and at run time ON or OFF is reported, so I would expect to be able to set the value with ON or OFF in my.cnf file.

This is somewhat related to Bug #44509 and Bug #62986.

How to repeat:
Set my.cnf entry to the following:
innodb_use_native_aio=OFF

Verify with this query:
show variables like 'innodb_use_native_aio';

Suggested fix:
Allow ON/OFF, 1/0, and true/false to work as valid values. At a minimum ON/OFF and 1/0.

[28 Oct 2011 3:15] Valeriy Kravchuk

As 5.5 manual (http://dev.mysql.com/doc/refman/5.5/en/dynamic-system-variables.html) still says that you should use numeric values in my.cnf, this is a duplicate/another example of Bug #44509.