[MDEV-31038] Parallel Replication Breaks if XA PREPARE Fails Updating Slave GTID State - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.5, 10.6, 10.11, 11.1(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 11.0(EOL)
Fix Version/s: 11.1.1, 10.11.3, 11.0.2, 10.5.20, 10.6.13, 10.8.8, 10.9.6, 10.10.4
Component/s: Replication
Labels:
None

Description

Similar to ~~MDEV-29642~~, but instead of a slave crashing, if a parallel slave executing an XA PREPARE fails the follow up autocommit transaction due to a temporary error which can be retried (e.g. a deadlock when trying to lock mysql.gtid_slave_pos), then the retry will run into the same issue as ~~MDEV-29642~~, i.e. an out-of-order GTID attempt (if gtid strict mode is enabled) or XID already exists (otherwise).

This is because the XA PREPARE had already committed successfully in binlog and storage engines, and only the slave GTID state update failed. Then on retry, the transaction has already been seen, so we error.

Filed as a separate ticket (rather than extending ~~MDEV-29642~~ scope) because this is specific to the parallel slave, and may need a separate effort.

Attachments

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

rpl_parallel_optimistic.test
2 kB
2023-04-25 12:49

Issue Links

is caused by

MDEV-31185 rw_trx_hash_t::find() unpins pins too early

Closed

relates to

MDEV-21777 Implement crash-safe execution the user XA on binlog-less slave

Open

MDEV-31185 rw_trx_hash_t::find() unpins pins too early

Closed

MDEV-29642 Server Crash During XA Prepare Can Break Replication

Closed

Activity

People

Assignee:: Vladislav Lesin

Reporter:: Brandon Nesterenko

Votes:: 2 Vote for this issue

Watchers:: 12 Start watching this issue

Dates

Created:: 2023-04-11 21:42

Updated:: 2024-07-07 19:37

Resolved:: 2023-06-12 20:49

Git Integration

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