[MDEV-15143] InnoDB: Rollback of trx with id 0 completed Created: 2018-01-31  Updated: 2018-01-31  Resolved: 2018-01-31

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.2, 10.3.0
Fix Version/s: 10.2.13, 10.3.5

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: recovery

Issue Links:
Relates
relates to MDEV-15132 Avoid accessing the TRX_SYS page Closed

 Description   

This bug came up in the MDEV-15132 testing. When InnoDB has completed the rollback of a recovered transaction, it used to display the transaction identifier. Starting with the change bug#16845421 INNODB: CRASH WHILE RECOVERING A TRANSACTION in MySQL 5.7.2 (and the merge of MySQL 5.7.9 to MariaDB 10.2.2) it would always display 0 instead:

2018-01-31  9:01:32 0 [Note] InnoDB: Rollback of trx with id 0 completed

The reason is that the trx->id would be reset at transaction commit.

 Comments   
Comment by Marko Mäkelä [ 2018-01-31 ]

While fixing this, I changed the message format:

2018-01-31 12:00:14 140691686427776 [Note] InnoDB: Trx id counter is 2304
 
2018-01-31 12:00:14 140691446613760 [Note] InnoDB: Starting in background the rollback of recovered transactions
 
…
 
2018-01-31 12:00:14 140691446613760 [Note] InnoDB: Rolled back recovered transaction 1286

Yes, we do output transaction identifiers in hexadecimal in some places, but not in the related Trx id counter message above.

Generated at Thu Feb 08 08:19:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.