Mysql XA transaction recovery_mysql

Mysql XA transaction recovery bitsCN.com

Mysql XA transaction recovery

Mysql database boot error:

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

100224 12:24:20 InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the. ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

InnoDB: Transaction 0 4497755 was in the XA prepared state.

InnoDB: Transaction 0 4468551 was in the XA prepared state.

InnoDB: Transaction 0 4468140 was in the XA prepared state.

InnoDB: 3 transaction (s) which must be rolled back or cleaned up

InnoDB: in total 0 row operations to undo

InnoDB: Trx id counter is 0 5312768.

InnoDB: Starting in background the rollback of uncommitted transactions

100224 12:24:20 InnoDB: Rollback of non-prepared transactions completed

100224 12:24:20 InnoDB: Started; log sequence number 0 3805002509

100224 12:24:20 InnoDB: Starting recovery for XA transactions...

100224 12:24:20 InnoDB: Transaction 0 4497755 in prepared state after recovery

100224 12:24:20 InnoDB: Transaction contains changes to 8 rows

100224 12:24:20 InnoDB: Transaction 0 4468551 in prepared state after recovery

100224 12:24:20 InnoDB: Transaction contains changes to 1 rows

100224 12:24:20 InnoDB: Transaction 0 4468140 in prepared state after recovery

100224 12:24:20 InnoDB: Transaction contains changes to 1 rows

100224 12:24:20 InnoDB: 3 transactions in prepared state after recovery

100224 12:24:20 [Note] Found 3 prepared transaction (s) in InnoDB

100224 12:24:20 [Warning] Found 3 prepared XA transactions

100224 12:24:20 [Note] Event schedents: Loaded 0 events

100224 12:24:20 [Note]/opt/mysql/bin/mysqld: ready for connections.

Version: '5. 1.39 'socket:'/tmp/mysql. sock 'port: 3306 MySQL Community Server (GPL)

This means that three XA transactions are not committed or rolled back.

Log on to mysql

Mysql> xa recover;

+ ---------- + -------------- + ------------------------------------------------------------ +

| FormatID | gtrid_length | bqual_length | data |

+ ---------- + -------------- + ------------------------------------------------------------ +

| 131075 | 30 | 28 | 1-7f000001: bae5: 4b6928eb: f06108f000001: bae5: 4b6928eb: f0650 |

| 131075 | 30 | 28 | 1-7f000001: bae5: 4b6928eb: fb5c37f000001: bae5: 4b6928eb: fb5cd |

| 131075 | 30 | 28 | 1-7f000001: bae5: 4b6928eb: f03ea7f000001: bae5: 4b6928eb: f0400 |

+ ---------- + -------------- + ------------------------------------------------------------ +

The data representation is as follows:

FormatIDis the formatIDpart of the transaction xid

Gtrid_lengthis the length in bytes of the gtridpart of the xid

Bqual_lengthis the length in bytes of the bqualpart of the xid

Datais the concatenation of the gtridand bqualparts of the xid

This is information about the three XA transactions and is ready to be rolled back directly.

Mysql> xa rollback '1-7f000001: bae5: 4b6928eb: fb5c3 ', '7f000001: bae5: 4b6928eb: fb5cd', 131075;

Query OK, 0 rows affected (0.41 sec)

It is normal to start again.

BitsCN.com