Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.13, 10.5.14
-
- OS: Debian 11 \
- Sys/Kernel info: Linux theflashbox 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux \
- Type: Physical server \
- Tested on MariaDB versions: 10.5.13 and 10.5.14 \
- Galera version: galera-4 : 26.4.9, 26.4.10 and 26.4.11
- Hardware specifications:
* raid1 - nvme, 4.0T
* Memory: 128G, CPU(s): 32 (2 threads per core, 16 cores per socket, 1 socket)
* Model name: AMD Ryzen 9 5950X 16-Core Processor
* Architecture: x86_64- OS: Debian 11 \ - Sys/Kernel info: Linux theflashbox 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux \ - Type: Physical server \ - Tested on MariaDB versions: 10.5.13 and 10.5.14 \ - Galera version: galera-4 : 26.4.9, 26.4.10 and 26.4.11 - Hardware specifications: * raid1 - nvme, 4.0T * Memory: 128G, CPU(s): 32 (2 threads per core, 16 cores per socket, 1 socket) * Model name: AMD Ryzen 9 5950X 16-Core Processor * Architecture: x86_64
Description
Current infrastructure:
1. Galera cluster (GC1) running MariaDB 10.3.32
2. Galera cluster (GC2) running MariaDB 10.5.13 (tested also on 10.5.14)
3. Asynchronous replication setup from GC1 -> GC2
4. Both clusters have SSL configured
5. Active traffic on GC1 (on node1 only)
Working Scenario:
1. GC2 running with 3-cluster members: up and running
2. Replication configured between GC1 (node1) -> GC2 (node1): up and running
Crash:
1. On GC2 (node1), stop mariadb, and start -> Crash
2. Repeats the same messages on each start attempt
Workaround:
- Add skip_replica_start in configuration file and start mariadb: OK
- Then start replica threads (io_thread, sql_thread): Replication up and running
> Note: Most of the time also fixes "Node dropped from cluster" error message.
Crash Report: (attached as error.log_bug.txt)
Can it be related to the mariadb_upgrade? (https://jira.mariadb.org/browse/MDEV-27789)
Thanking you for checking.