[MDEV-22398] mariabackup.innodb_xa_rollback fails on repeat Created: 2020-04-28  Updated: 2020-08-11  Resolved: 2020-05-18

Status: Closed
Project: MariaDB Server
Component/s: mariabackup
Affects Version/s: 10.2.32, 10.3.23, 10.4.13
Fix Version/s: 10.5.4, 10.2.33, 10.3.24, 10.4.14

Type: Bug Priority: Blocker
Reporter: Vladislav Lesin Assignee: Vladislav Lesin
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Blocks
Relates
relates to MDEV-22656 Document what rollback-xa mariabackup... Closed
relates to MDEV-21168 Active XA transactions stop slave fro... Closed
relates to MDEV-22614 "mariabackup --prepare" exits with co... Closed

 Description   

When MTR used with --repeat option the test fails with the following error:

mariabackup.innodb_xa_rollback 'innodb'  w52 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2020-04-27 14:32:54
 
line
 
2020-04-27 14:32:03 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 1639453 is in the future! Current system log sequence number 1639445.
 
2020-04-27 14:32:03 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
 
2020-04-27 14:32:03 0 [ERROR] InnoDB: Page [page id: space=0, page number=311] log sequence number 1639453 is in the future! Current system log sequence number 1639445.
 
2020-04-27 14:32:03 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
 
^ Found warnings in /dev/shm/10.3/mysql-test/var/52/log/mysqld.1.err



 Comments   
Comment by Geoff Montee (Inactive) [ 2020-05-12 ]

When this fix is released, we will need to modify the warning from the KB's entry on --rollback-xa:

https://mariadb.com/kb/en/mariabackup-options/#-rollback-xa

Generated at Thu Feb 08 09:14:27 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.