Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2, 10.3.0
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.
Attachments
Issue Links
- relates to
-
MDEV-15132 Avoid accessing the TRX_SYS page
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| issue.field.resolutiondate | 2018-01-31 10:13:16.0 | 2018-01-31 10:13:16.227 |
| Fix Version/s | 10.3.5 [ 22905 ] | |
| Fix Version/s | 10.2.13 [ 22910 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 85335 ] | MariaDB v4 [ 153698 ] |
While fixing this, I changed the message format:
2018-01-31 12:00:14 140691686427776 [Note] InnoDB: Trx id counter is 23042018-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 1286Yes, we do output transaction identifiers in hexadecimal in some places, but not in the related Trx id counter message above.