[MDEV-32551] "Read semi-sync reply magic number error" warnings on master - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.6
Fix Version/s: 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3
Component/s: Replication
Labels:
None
Environment:
Master and single semi-sync slave

Description

The user gets a lot of these errors randomly in the error log:

"Read semi-sync reply magic number error"

This is probably some missing or out of sync packet as part of semi sync replication.

We should try to repeat this by have our QA and benchmark teams run tests on a master and semi-sync slave to try to repeat the issue.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

skr.test
3 kB
2023-11-06 17:05
skr.cnf
0.2 kB
2023-11-06 17:04

Issue Links

causes

MDEV-32940 Semi-sync Slave Falsely Logs that Master has Semi-sync Disabled

Closed

MDEV-32943 Stopping Semi-sync Slave Reports that it is Falling Back to Async Mode

Closed

MDEV-32944 Rpl_semi_sync_slave_enabled sysvar Should Not Be Modifiable While IO Thread is Running

Closed

MDEV-32945 Rpl_semi_sync_master_status is ON Without Any Connected Slaves

Open

MDEV-32947 Semi-sync with Multi-source Checksum Verification Failure

Confirmed

MDEV-32960 Semi-sync ACKed Transaction can Timeout and Switch Off Semi-sync with Multiple Replicas

Closed

MDEV-32961 Semi-sync Primary Segfaults on Net Error

Closed

MDEV-33331 IO Thread Relay Log Inconsistent Statistics After MDEV-32551

Open

MDEV-33546 Rpl_semi_sync_slave_status is ON When Replication Is Not Configured

Closed

MDEV-39583 Replace the slave-side graceful self-KILL with the master-side COM_QUIT handing in Semi-Synchronous Replication

In Progress

relates to

MDEV-11853 semisync thread can be killed after sync binlog but before ACK in the sync state

Closed

MDEV-24773 slave_compressed_protocol doesn't work properly with semi-sync replication

Closed

MDEV-28114 Semi-sync Master ACK Receiver Thread Can Error on COM_QUIT

Closed

MDEV-28141 Slave crashes with Packets out of order when connecting to a shutting down master

Open

MDEV-28306 Slave I/O: Fatal error: Failed to run 'after_read_event' hook, Internal MariaDB error code: 1593

Open

MDEV-29369 rpl.rpl_semi_sync_shutdown_await_ack fails regularly with Result content mismatch

Closed

MDEV-32365 detailize the semisync replication magic number error

Closed

MDEV-32385 Semi-Sync Ack_Receiver Thread Should Allow COM_QUIT Command

Closed

MDEV-32792 Second Semi-sync Replica Can Hang at Connect Time

Closed

MDEV-33327 rpl_seconds_behind_master_spike Sensitive to IO Thread Stop Position

Closed

MXS-4792 Semi-sync replication through MaxScale causes errors on STOP SLAVE

Closed

MXS-4793 Unknown command errors when semi-sync replication runs through MaxScale

Closed

(5 causes, 12 relates to)

Activity

People

Assignee:: Michael Widenius

Reporter:: Michael Widenius

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Dates

Created:: 2023-10-23 10:43

Updated:: 2026-05-13 22:17

Resolved:: 2024-01-23 15:17

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

15d 1h 23m

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.