[MDEV-27740] Joiner node failed to join the cluster when saving redo_logs in a directory different from the data directory Created: 2022-02-03  Updated: 2022-04-05  Resolved: 2022-04-05

Status: Closed
Project: MariaDB Server
Component/s: Galera SST
Affects Version/s: 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3, 10.8.2
Fix Version/s: 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3, 10.9.1

Type: Bug Priority: Critical
Reporter: Ramesh Sivaraman Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Issue split
split from MDEV-27524 Incorrect binlogs after Galera SST us... Closed

 Description   

Joiner node failed to join the cluster when saving redo_logs in a directory different from the data directory
config info

n1.cnf

innodb_data_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/innodb1
innodb_log_group_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/iblog1

n2.cnf

innodb_data_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/innodb2
innodb_log_group_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/iblog2

[00] 2022-02-02 09:20:03 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/node1/node1_socket.sock
[00] 2022-02-02 09:20:03 Using server version 10.2.42-MariaDB
/test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt//bin/mariabackup based on MariaDB server 10.2.42-MariaDB Linux (x86_64)
[00] 2022-02-02 09:20:03 uses posix_fadvise().
[00] 2022-02-02 09:20:03 cd to /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/node1/
[00] 2022-02-02 09:20:03 open files limit requested 0, set to 1048576
[00] 2022-02-02 09:20:03 mariabackup: using the following InnoDB configuration:
[00] 2022-02-02 09:20:03 innodb_data_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/innodb1
[00] 2022-02-02 09:20:03 innodb_data_file_path = ibdata1:12M:autoextend
[00] 2022-02-02 09:20:03 innodb_log_group_home_dir = /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/iblog1
[00] 2022-02-02 09:20:03 InnoDB: Using Linux native AIO
2022-02-02  9:20:03 23349101111232 [Note] InnoDB: Number of pools: 1
2022-02-02  9:20:03 23349101111232 [Warning] InnoDB: Unable to open "/test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/iblog1/ib_logfile0" to check native AIO read support.
2022-02-02  9:20:03 23349101111232 [Warning] InnoDB: Linux Native AIO disabled.
2022-02-02  9:20:03 23349101111232 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2022-02-02  9:20:03 23349101111232 [ERROR] InnoDB: The error means the system cannot find the path specified.
2022-02-02  9:20:03 23349101111232 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2022-02-02  9:20:03 23349101111232 [ERROR] InnoDB: File /test/mtest/GAL_MD280122-mariadb-10.2.42-linux-x86_64-opt/iblog1/ib_logfile0: 'open' returned OS error 71. Cannot continue operation
220202  9:20:03 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.



 Comments   
Comment by Jan Lindström (Inactive) [ 2022-02-09 ]

ok to push

Comment by Julius Goryavsky [ 2022-04-05 ]

Merged & fixed by MDEV-27524

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