Details
Description
Executing a STOP SLAVE on a replicating server which uses semi-sync causes an error to be logged on the server.
server4 | 2023-10-05 7:37:32 34 [Note] Error reading relay log event: slave SQL thread was killed
|
server4 | 2023-10-05 7:37:32 34 [Note] Slave SQL thread exiting, replication stopped in log 'binlog.000002' at position 684; GTID position '0-3000-11', master: 127.0.0.1:4006
|
server4 | 2023-10-05 7:37:32 33 [Note] Slave I/O thread exiting, read up to log 'binlog.000002', position 684; GTID position 0-3000-11, master 127.0.0.1:4006
|
server1 | 2023-10-05 7:37:32 13 [ERROR] Read semi-sync reply magic number error
|
This happens because the COM_QUIT packet sent by MaxScale is unconditionally sent when the connections are terminating and the replication protocol does not normally send it.
Attachments
Issue Links
- relates to
-
MDEV-32385 Semi-Sync Ack_Receiver Thread Should Allow COM_QUIT Command
-
- Closed
-
-
-
- Closed
-