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

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.0.29, 10.1.21, 10.2.3
Fix Version/s: 10.7.4, 10.4.25, 10.5.16, 10.6.8, 10.8.3
Component/s: Replication
Labels:
None

Description

Shutdown of master in semisync when it's in sync can let more transactions in the master than the slaves.
This is expected in case of a crash as the binlog write before send and wait for the ACK. But this is an issue in case of regular shutdown, as the workload can not be safely be moved to a slave.

We can make sure the semi sync thread is killed last in shutdown and stopped only if status move to no sync or after receiving the ACK , this would possibly delay shutdown for the maximum time of the rpl_semi_sync_master_timeout

Attachments

Issue Links

relates to

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-29369 rpl.rpl_semi_sync_shutdown_await_ack fails regularly with Result content mismatch

Closed

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

Closed

Activity

People

Assignee:: Brandon Nesterenko

Reporter:: VAROQUI Stephane

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2017-01-20 11:16

Updated:: 2024-04-25 10:28

Resolved:: 2022-04-22 21:50

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

14d 5.75h

Git Integration

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