Mysql XA transaction recovery

Mysql XA transaction recovery mysql database boot error: www.2cto.com 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. 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 I NnoDB: 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 t O 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 Scheduler: 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) means that three XA transactions are not committed or rolled back. Log on to mysql> xa recover; + ---------- + -------------- + ------------ + response + | formatID | gtrid_length | bqual_length | data | + ---------- + -------------- + ------------ + response + | 131075 | 30 | 28 | expires: bae5: expires: f06108f000001: bae5: 4b6928eb: f0650 | 131075 | 30 | 28 | 1-7f000001: Bae5: 4b6928eb: pushed: bae5: 4b6928eb: fb5cd | 131075 | 30 | 28 | 1-7f000001: bae5: 4b6928eb: pushed: bae5: 4b6928eb: f0400 | + ---------- + -------------- + ---------------------------------------------------------- + the data representation information is as follows: formatIDis the formatIDpart of the transaction xid gtrid_lengthis length in bytes of the gtridpart of the xid bqual_lengthis length in bytes of th E bqualpart of the xid datais the concatenation of the gtridand bqualparts of the xid is the information of the three XA transactions, ready to roll 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.