mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2026-05-15 19:37:16 +02:00
Code Issues Projects Releases Packages Wiki Activity

MDEV-14545 Backup fails due to MLOG_INDEX_LOAD record

Browse source 
Problem:
=======
  Mariabackup exits during prepare phase if it encounters
MLOG_INDEX_LOAD redo log record. MLOG_INDEX_LOAD record
informs Mariabackup that the backup cannot be completed based
on the redo log scan, because some information is purposely
omitted due to bulk index creation in ALTER TABLE.

Solution:
========
Detect the MLOG_INDEX_LOAD redo record during backup phase and
exit the mariabackup with the proper error message.
This commit is contained in:
Thirunarayanan Balathandayuthapani 2018-03-13 15:19:30 +05:30
commit ff909acfa4
5 changed files with 268 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

46
mysql-test/suite/mariabackup/unsupported_redo.result Normal file
View file

@ -0,0 +1,46 @@
call mtr.add_suppression("InnoDB: New log files created");
call mtr.add_suppression("InnoDB: Operating system error number .* in a file operation");
call mtr.add_suppression("InnoDB: The error means the system cannot find the path specified");
call mtr.add_suppression("InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them");
call mtr.add_suppression("InnoDB: Ignoring tablespace for `test`\\.`t21` because it could not be opened");
call mtr.add_suppression("InnoDB: Cannot open datafile for read-only: ");
call mtr.add_suppression("Table .* in the InnoDB data dictionary has tablespace id .*, but tablespace with that id or name does not exist");
CREATE TABLE t1(i INT PRIMARY KEY auto_increment, a int) ENGINE INNODB;
alter table t1 FORCE, algorithm=inplace;
# Fails during full backup
DROP TABLE t1;
CREATE TABLE t1(i INT PRIMARY KEY auto_increment, a int) ENGINE INNODB;
INSERT INTO t1(a) select 1 union select 2 union select 3;
# Create full backup , modify table, then fails during creation of
# incremental/differential backup
alter table t1 force, algorithm=inplace;
drop table t1;
CREATE TABLE t1(i INT) ENGINE INNODB;
INSERT INTO t1 VALUES(1);
CREATE TABLE t21(i INT) ENGINE INNODB;
INSERT INTO t21 VALUES(1);
CREATE TABLE t2(i int) ENGINE INNODB;
ALTER TABLE t21 FORCE, ALGORITHM=INPLACE;
# Create partial backup (excluding table t21), Ignore the
# unsupported redo log for the table t21.
t1.frm
t1.ibd
t2.frm
t2.ibd
# After partial restore operation, t21 files will be missing but t21
# table information will be present in dictionary. It will
# restrict creating the table t21 in the future test. To avoid
# that, take the copy of t21 files and drop the table later.
# Prepare the full backup
# shutdown server
# remove datadir
# xtrabackup move back
# restart server
SHOW TABLES;
Tables_in_test
t1
t2
DROP TABLE t1;
DROP TABLE t2;
# Move the t21 files into data directory
DROP TABLE t21;