MySQL Bugs: #86676: MASTER_HEARTBEAT_PERIOD not properly set while upgrading MySQL.

Bug #86676	MASTER_HEARTBEAT_PERIOD not properly set while upgrading MySQL.
Submitted:	13 Jun 2017 5:36	Modified:	15 Jun 2017 7:00
Reporter:	Pu Hot	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.7	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
After in-place upgrade of MySQL Database from 5.6.29 to 5.7.17, MASTER_HEARTBEAT_PERIOD will inherit value 1800.00 from the old master.info, which will cause a problem to the replication thread. 

How to repeat:
To reproduce this problem:
Set up a master-slave group of MySQL 5.6, then in-place upgrade to MySQL 5.7.
You will see these information in master's error log.
2017-06-05T10:14:24.983922Z 459 [Note] While initializing dump thread for slave with UUID <d2dbcecc-e485-11e5-9faf-008cfa5c6850>, found a zombie dump thread with the same UUID. Master is killing the zombie dump thread(458).
2017-06-05T10:14:24.983993Z 459 [Note] Start binlog_dump to master_thread_id(459) slave_server(2201033306), pos(mysql-bin.000574, 154)
2017-06-05T10:15:25.050421Z 460 [Note] While initializing dump thread for slave with UUID <d2dbcecc-e485-11e5-9faf-008cfa5c6850>, found a zombie dump thread with the same UUID. Master is killing the zombie dump thread(459).
2017-06-05T10:15:25.050500Z 460 [Note] Start binlog_dump to master_thread_id(460) slave_server(2201033306), pos(mysql-bin.000574, 154)
2017-06-05T10:16:25.116947Z 461 [Note] While initializing dump thread for slave with UUID <d2dbcecc-e485-11e5-9faf-008cfa5c6850>, found a zombie dump thread with the same UUID. Master is killing the zombie dump thread(460).

and these information bellow in slave's error log:
2017-06-05T10:09:24.684694Z 31 [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.
2017-06-05T10:10:24.727390Z 31 [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.
2017-06-05T10:11:24.793976Z 31 [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.
2017-06-05T10:12:24.861014Z 31 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended.

Hello!

Thank you for the report.
I can assume it is a "Note" i.e "[Note] While initializing dump thread for slave with UUID <xxxxx-xxxx-xxx-xxxx-xxxxxx>, found a zombie dump thread with the same UUID. Master is killing the zombie dump thread(<number>)" Post Bug #72578 fix,  a NOTE is added on master's error log file when log_warnings is greater than 1. 

Please see the detailed explanation in Bug #84358 by Sven Sandberg, he explained the cases in which this "Note" is observed, and why this is expected behavior.

Second one i.e and in slave's error log:
*** [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

This is reported here and handled as part of Bug #75261.

Thanks,
Umesh

Hi

This report is NOT a duplicate of Bug #75261, the main idea is MASTER_HEARTBEAT_PERIOD is not properly set after upgrading from 5.6 to 5.7, not a complain about error logs.