MySQL Bugs: #72067: skip_name_resolve should be a dynamic setting

Bug #72067	skip_name_resolve should be a dynamic setting
Submitted:	18 Mar 2014 12:09	Modified:	18 Mar 2014 13:00
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Options	Severity:	S4 (Feature request)
Version:	5.7.3	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	skip_name_resolve

Description:
skip_name_resolve is not dynamically configurable.

There are various blog posts on the Internet suggesting that this should be set to ON and that may be good advice. The default value is OFF.  Currently to _test_ if the change is useful on a live system requires restarting mysqld and that is thus intrusive.

How to repeat:
root@server [(none)]> show global variables like 'skip_name_resolve';
+-------------------+-------+
| Variable_name     | Value |
+-------------------+-------+
| skip_name_resolve | OFF   |
+-------------------+-------+
1 row in set (0.00 sec)

root@server [(none)]> select @@version;
+---------------+
| @@version     |
+---------------+
| 5.7.3-m13-log |
+---------------+
1 row in set (0.00 sec)

root@server [(none)]> set global  skip_name_resolve = 1;
ERROR 1238 (HY000): Variable 'skip_name_resolve' is a read only variable
root@server [(none)]> 

Suggested fix:
Being able to do this dynamically would give much more flexibility to the DBA. I would not expect that making a setting like this dynamic should be too hard.  So it would be a good improvement to have.

Maybe this is something that can be done prior to MySQL 5.7 going GA? That would be nice.

FR verified as described.

set global skip_name_resolve = 1;
ERROR 1238 (HY000): Variable 'skip_name_resolve' is a read only variable

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_skip_name_reso...

duplicate of http://bugs.mysql.com/bug.php?id=71219

This FR is a duplicate of this one : http://bugs.mysql.com/bug.php?id=71219