[MXS-4793] Unknown command errors when semi-sync replication runs through MaxScale Created: 2023-10-05  Updated: 2023-10-24  Resolved: 2023-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: readconnroute, readwritesplit
Affects Version/s: 6.4.10
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: CS0653958

Issue Links:
Relates
relates to MDEV-32551 "Read semi-sync reply magic number er... Closed
Sprint: MXS-SPRINT-192

 Description    

server4  | 2023-10-05  8:42:04 49 [ERROR] Error reading packet from server: Unknown command (server_errno=1047)
 
server4  | 2023-10-05  8:42:04 49 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'binlog.000002' at position 3948; GTID position '0-3000-27'
 
server1  | 2023-10-05  8:42:04 13 [ERROR] Read semi-sync reply magic number error
 
server1  | 2023-10-05  8:42:04 73 [Note] Start binlog_dump to slave_server(3003), pos(binlog.000002, 3948), using_gtid(1), gtid('0-3000-27')
 
server1  | 2023-10-05  8:42:04 72 [Note] Stop semi-sync binlog_dump to slave (server_id: 3003)



 Comments   
Comment by markus makela [ 2023-10-10 ]

This was most likely a side-effect of MXS-4792 and with it fixed, I can no longer reproduce it.

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