[MDEV-14936] Test MariaDB Backup 10.1 against newest versions of 5.5 and 10.0 Created: 2017-05-04  Updated: 2018-01-12  Resolved: 2017-10-27

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Ralf Gebhardt Assignee: Andrii Nikitin (Inactive)
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14172 mariabackup doesn't store innodb_fast... Closed
relates to MDEV-14174 crash on start with innodb-track-chan... Closed
relates to MDEV-14175 backup shows corruption for 5.5 Serve... Closed
relates to MDEV-14176 XtraDB files with innodb_page_size in... Closed
relates to MDEV-14177 Document comand FLUSH CHANGED_PAGE_BI... Closed
relates to MDEV-14937 Test final version of MariaDB Backup ... Closed

 Description   

The first version of MariaDB Backup was added to 10.1.23. As we now support also Windows we can expect to get questions from users/customers about supporting 10.0 and 5.5.

It would be good to test MariaDB Backup against the newest versions of MariaDB Server 5.5 and 10.0. and to add the information to the table https://mariadb.com/kb/en/mariadb/mariadb-backup/ in a "Compatibility" column



 Comments   
Comment by Andrii Nikitin (Inactive) [ 2017-05-04 ]

With environs framework I did following actions to deploy tar packages and run xtrabackup tests with then:

./replant.sh m2-10.0.30
m2-10.0.30/download.sh
./replant.sh m3-5.5.55
m3-5.5.55/download.sh
./replant.sh m6-10.1.23
m6-10.1.23/download.sh
 
# first test 10.1.23 alone just in case
./runsuite.sh m6 _plugin/xtrabackup/t
...
Duration=345
Passes=136
Failures=0
 
# now test 10.0.30 with mariabackup from 10.1.23
./runsuite.sh m6 m2 _plugin/xtrabackup/t
Duration=281
Passes=132
Failures=4
 
# now test 5.5.55 with mariabackup from 10.1.23
./runsuite.sh m6 m3 _plugin/xtrabackup/t
...
Duration=162
Passes=112
Failures=17

Failures in 10.0 are in tests xb_incremental_compressed_bitmap* and rather internal problems of the framework, which needs to be adjusted to 10.0

Almost all failures in 5.5 are related to crashes of mariabackup during incremental backup.

Conclusion:
mariabackup 10.1.23 works “well enough” with 10.0.30 MariaDB Server
mariabackup 10.1.23 works “well enough” with 5.5.55 MariaDB Server, excluding incremental backup.
“Well enough” = considering Alpha status of the release

Comment by Andrii Nikitin (Inactive) [ 2017-05-04 ]

Percona-XtraBackup 2.3.8 handles these tests better for 5.5.55 , maybe work for another todo:

./replant.sh x9-system
sudo x9-system/install.sh 2.3.8
./runsuite.sh m3 x9 _plugin/xtrabackup/t
...
Duration=155
Passes=122
Failures=8

Comment by Andrii Nikitin (Inactive) [ 2017-05-04 ]

The same tests with InnoDB plugin:

mkdir m2-10.0.30/config_load
cp m2-10.0.30/configure_innodb_plugin.sh m2-10.0.30/config_load/
./runsuite.sh m6 m2 _plugin/xtrabackup/t
...
FAILED tests :
_plugin/xtrabackup/t/remote_tablespaces.sh
Duration=215
Passes=127
Failures=1
 
mkdir m3-5.5.55/config_load
cp m3-5.5.55/configure_innodb_plugin.sh m3-5.5.55/config_load/
./runsuite.sh m6 m3 _plugin/xtrabackup/t
...
Duration=151
Passes=108
Failures=8
 
./runsuite.sh m3 x9 _plugin/xtrabackup/t
...
Duration=143
Passes=117
Failures=0

With InnoDB plugin, 10.0.30 and 5.5.55 have less failures because some tests don't run . Crashes for incremental backup for mariabackup in 5.5.55 are still observed even with innodb plugin.

Comment by Elena Stepanova [ 2017-05-04 ]

anikitin,

Please make sure all real failures (those that aren't caused by the tool/environment) are filed as separate bugs in JIRA/MDEV. It was desirable before the release, but after it's gone public it's mandatory.

Comment by Andrii Nikitin (Inactive) [ 2017-10-27 ]

Testing current 10.1 tree:
5.5 failures:
FAILED tests :
_plugin/xtrabackup/t/bug1112224.sh
_plugin/xtrabackup/t/bug733651.sh
_plugin/xtrabackup/t/ib_incremental_bitmap_lsn.sh
_plugin/xtrabackup/t/ib_incremental_bitmap.sh
_plugin/xtrabackup/t/ib_incremental_force_full_scan.sh
_plugin/xtrabackup/t/ib_lru_dump_stream.sh
_plugin/xtrabackup/t/innodb_fast_checksum.sh
_plugin/xtrabackup/t/innodb_page_size.sh
_plugin/xtrabackup/t/xb_incremental_bitmap_misc.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_16kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_2kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_4kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_8kb.sh
Host=UBINTI
Extra=
Concurrency=10
Timeout=1
Duration=121
Passes=98
Failures=13

bug1112224.sh - happened once, couldn't reproduce
bug733651.sh - (minor problem) - MDEV-14172
ib_incremental_bitmap*.sh , ib_incremental_force_full_scan, xb_bitmap (8 failures) - (not a backup problem) - MDEV-14174
innodb_fast_checksum.sh - (probably minor problem) MDEV-14175
innodb_page_size.sh - MDEV-14176

Comment by Andrii Nikitin (Inactive) [ 2017-10-27 ]

10.0 tests all passed except xb_incremental_compressed_bitmap* , which is probably cannot run in 10.0
Related documentation request as been opened MDEV-14177
FAILED tests :
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_16kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_2kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_4kb.sh
_plugin/xtrabackup/t/xb_incremental_compressed_bitmap_8kb.sh
Host=UBINTI
Extra=
Concurrency=10
Timeout=300
Duration=197
Passes=111
Failures=4

Comment by Andrii Nikitin (Inactive) [ 2017-10-27 ]

For reference: steps to perform tests:
1. setup framework

git clone http://github.com/AndriiNikitin/mariadb-environs
cd mariadb-environs
./get_plugin.sh xtrabackup

2. Build 5.5, 10.0 and 10.1 environs. Code below will build 10.1 from source (m1) and download and configure 5.5 (m2) and 10.0 (m3) tar packages:

./replant.sh m1-10.1
./replant.sh m2-5.5.58
./replant.sh m3-10.0.36
./build_or_download.sh m1
./build_or_download.sh m2
./build_or_download.sh m3

3. Optionally test 10.1 and see if any failure

./runsuite.sh m1 _plugin/xtrabackup/t

4. Test 5.5 and 10.0 with commands below:

./runsuite.sh m1 m2 _plugin/xtrabackup/t
./runsuite.sh m1 m3 _plugin/xtrabackup/t

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