Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.26, 10.1.41, 10.3.17, 10.4.7
Description
The "Start binlog_dump" message hasn't been updated to include the slave's requested GTID position:
2019-08-25 20:05:05 139836760311552 [Note] Start binlog_dump to slave_server(2), pos(, 4)
|
See here:
https://github.com/MariaDB/server/blob/mariadb-10.4.7/sql/sql_repl.cc#L2111
For diagnostic purposes, I think it would be helpful if the GTID position were included. For example, maybe the message could be updated to something like this:
2019-08-25 20:05:05 139836760311552 [Note] Start binlog_dump to slave_server(2), pos(, 4), using_gtid(1), gtid('1-1-201,2-2-100')
|
2019-08-25 20:05:05 139836760311552 [Note] Start binlog_dump to slave_server(3), pos('mariadb-bin.004142', 507988273), using_gtid(0), gtid('')
|
I do see that the GTID position is available in the connect_gtid_state variable:
https://github.com/MariaDB/server/blob/mariadb-10.4.7/sql/sql_repl.cc#L2091
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-