[MDEV-28968] mariabackup SST doesn't properly handle --innodb-buffer-pool-filename Created: 2022-06-27  Updated: 2022-11-15  Resolved: 2022-11-15

Status: Closed
Project: MariaDB Server
Component/s: Galera SST, mariabackup
Affects Version/s: 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3, 10.9.1, 10.10
Fix Version/s: 10.10.1, 10.3.37, 10.4.27, 10.5.18, 10.6.11, 10.7.7, 10.8.6, 10.9.4

Type: Bug Priority: Major
Reporter: Julius Goryavsky Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Issue split
split from MDEV-28758 Mariabackup copies binary logs to bac... Closed
Relates
relates to MDEV-27524 Incorrect binlogs after Galera SST us... Closed
relates to MDEV-29591 nesting innodb subdirectories in data... Stalled

 Description   

The mariabackup SST script cannot properly handle SST on the joiner side if a non-standard filename is specified in the --innodb-buffer-pool-filename option. An example log file that shows that the received file is being copied to the destination directory under the original name ib_buffer_pool, and not under the name given with the option specified on the command line:

[01] 2022-06-28 01:04:42 Moving ./xtrabackup_info to /home/panda/mariadb-10.3/build/mysql-test/var/mysqld.2/data/xtrabackup_info
 
[01] 2022-06-28 01:04:42         ...done
 
[01] 2022-06-28 01:04:42 Moving ib_buffer_pool to /home/panda/mariadb-10.3/build/mysql-test/var/mysqld.2/innodb_data2/ib_buffer_pool
 
[01] 2022-06-28 01:04:42         ...done
 
[00] 2022-06-28 01:04:42 completed OK!



 Comments   
Comment by Julius Goryavsky [ 2022-11-15 ]

Main part fixed with MDEV-28781, but there is a part that refers to the case of nesting a separate directory for innodb_buffer_pool in datadir, but this only applies to rsync mode and will be fixed in MDEV-29591

Generated at Thu Feb 08 10:04:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.