Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
Description
Elaborated MDEV-32347 description test demonstrates how a prepared user XA transaction
gets rolled back:
CREATE TABLE ti (c INT KEY) engine=Innodb;
|
XA START 'xid_i'; |
INSERT INTO ti VALUES (1); |
XA END 'xid_i'; |
XA PREPARE 'xid_i'; |
|
# --error ER_XAER_RMFAIL
|
LOAD INDEX INTO CACHE c KEY(PRIMARY);
|
|
XA COMMIT 'xid_i'; |
|
SELECT count(*) = 1 FROM ti; |
# => 0 (sic!) |
LOAD INDEX INTO CACHE and CACHE INDEX ... must also error out which is not done (by at least LOAD INDEX) either.
No other sql commands, form either DML:s or DDL:s class, are found to produce similar effect.
Attachments
Issue Links
- relates to
-
MDEV-26124 Minor LOAD INDEX output inconsistencies under XA
- Open
-
MDEV-31949 slow parallel replication of user xa
- Stalled
-
MDEV-32347 Stack smashing/looping, ASAN use-after-poison in xid_t::eq/event_xid_t::serialize, SIGSEGV in serialize_xid and Assertion `is_async_xac || thd->lex->xid->eq(thd->transaction->xid_state.get_xid())' failed in binlog_rollback_flush_trx_cache upon LOAD INDEX
- Closed
-
MDEV-34887 Assertion `!is_set() || (m_status == DA_EOF_BULK && is_bulk_op())' failed from mysql_admin_table on LOAD or CACHE INDEX
- Confirmed