[MDEV-28550] improper handling of replication event group that contains Gtid_log_list_event - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
Fix Version/s: 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3, 10.9.1
Component/s: Replication
Labels:
None

Description

It's legal to have Gtid_list_log_event inside a group. E.g
{{Gtid_event, Gtid_log_list_event, ... }} is permitted.
However, the slave IO thread treated both and Gtid_log_list_event specifically (see how to repeat)
as the terminal even when the group represents a DDL query.
That causes a premature Gtid state update so the slave IO would think
the whole group has been collected while in fact ... the actual terminal events are yet to be seen and process.

How to reproduce requires a 10.9 test:
./mtr rpl_mysqlbinlog_slave_consistency.test

Attachments

Activity

People

Assignee:: Brandon Nesterenko

Reporter:: Andrei Elkin

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2022-05-12 15:08

Updated:: 2022-06-09 10:48

Resolved:: 2022-06-09 10:48

Git Integration

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