[MDEV-13606] XA PREPARE transactions should survive innodb_force_recovery=1 or 2 - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Fix Version/s: 10.0.33, 10.1.27, 10.2.9, 10.3.2
Component/s: Backup, Storage Engine - InnoDB
Labels:
- 2PC
- XA
- recovery

Description

We should revert part of this InnoDB change in MySQL 5.0.3 (making innodb_force_recovery=1 and innodb_force_recovery=2 initiate rollback of a transaction that reached the XA PREPARE state before previous crash or shutdown) (March 2005).
It seems that the option tc_heuristic_recover=ROLLBACK in MySQL 5.0.3 (January 2005) was introduced for exactly this purpose; there was no need to convolute the logic of an already confusing InnoDB parameter.

Attachments

Issue Links

relates to

MDEV-13437 InnoDB fails to return error for XA COMMIT or XA ROLLBACK in read-only mode

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2017-08-21 13:29

Updated:: 2017-08-31 15:39

Resolved:: 2017-08-23 16:06

Git Integration

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