[MXS-4792] Semi-sync replication through MaxScale causes errors on STOP SLAVE Created: 2023-10-05  Updated: 2023-10-23  Resolved: 2023-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: Protocol
Affects Version/s: 6.4.10, 22.08.8, 23.02.4, 23.08.1
Fix Version/s: 6.4.11, 22.08.9, 23.02.5, 23.08.2

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Relates
relates to MDEV-32385 Semi-Sync Ack_Receiver Thread Should ... Open
relates to MDEV-32551 "Read semi-sync reply magic number er... Closed
Sprint: MXS-SPRINT-192

 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.


Generated at Thu Feb 08 04:31:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.