Bug #72629 Slave security warning printed too often
Submitted: 13 May 2014 8:14 Modified: 13 May 2014 8:37
Reporter: Hartmut Holzgraefe Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.6.16, 5.6.19 OS:Linux
Assigned to: CPU Architecture:Any

[13 May 2014 8:14] Hartmut Holzgraefe
Description:
The following warning is printed on every explicit and implicit start of the slave IO thread:

  [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.

If a slave reconnects often, e.g. as the network connection to the master is lost repeatedly, or when running into other connection problems like bug #72581, the error log is flooded with this kind of warnings though; and may confuse users trying to figure out the actual problem ...

How to repeat:
Set up replication "the old way" with user name and password in CHANGE MASTER,
start slave, then stop and restart the master mysqld a few times, see the warning printed on each reconnect ...

Suggested fix:
Only print this warning when explicitly receiving a START SLAVE command from a client (and maybe on the first implicit connect after a slave mysqld restart), but not on every automatic reconnect.
[13 May 2014 8:37] MySQL Verification Team
Hello Hartmut,

Thank you for the report/feature request!
Verified as described.

Thanks,
Umesh