MySQL Bugs: #91741: Improve Start binlog

Bug #91741	Improve Start binlog_dump log on master.
Submitted:	20 Jul 2018 14:06	Modified:	24 Jul 2018 20:32
Reporter:	Jean-François Gagné	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:	5.7.22	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Hi,

related to Bug#79517, but this previous bug is on the slave, and this new bug is for the master.

When a slave connect to the master, we can see this log if the slave is in MASTER_AUTO_POSITION = 0:

2018-07-20T13:56:41.319127Z 4 [Note] Start binlog_dump to master_thread_id(4) slave_server(300), pos(mysql-bin.000003, 194)

And this log if the slave is in MASTER_AUTO_POSITION = 1:

2018-07-20T13:57:28.613939Z 5 [Note] Start binlog_dump to master_thread_id(5) slave_server(300), pos(, 4)

Above include server_uuid and replication position in MASTER_AUTO_POSITION = 0 but many relevant informations are missing.  I can think of the following:

- server_uuid of the slave,
- ip, user and hostname of the connection,
- report_host, report_port, and report_user of the slave,
- GTID position of the slave.

Please consider adding those in the logs.  If you do not want to change the current log line, you could add more lines.

Many thanks,

JFG

How to repeat:
See description.

Hello Jean,

Thank you for the feature request!

regards,
Umesh

In the description, I write related to Bug#79517, but I should have written related to Bug#71565.  Sorry about that.