[MDEV-10497] Binlog recovery can break MariaDB Galera Cluster v10.0 Created: 2016-08-04  Updated: 2016-08-22  Resolved: 2016-08-22

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 10.0.26-galera
Fix Version/s: 10.0.27-galera

Type: Bug Priority: Major
Reporter: Andrew Garner Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Similar to the (now closed) MDEV-9423, binary log recovery can cause SST to fail due to binlog checkpoints not making it down to the binlog before xtrabackup copies the binlog. This was fixed in the 10.1.16 release, but I don't believe was reported against 10.0.

Here is snippet from the error log reproducing a similar failure under Debian 8.

160804  0:43:37 [Note] /usr/sbin/mysqld (mysqld 10.0.26-MariaDB-1~jessie-wsrep) starting as process 17669 ...
...
160804  0:44:01 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin
160804  0:44:01 [ERROR] Binlog file '/var/lib/mysql/mysql-bin.000003' not found in binlog index, needed for recovery. Aborting.
160804  0:44:01 [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}
160804  0:44:01 [ERROR] Can't init tc log
160804  0:44:01 [ERROR] Aborting


Generated at Thu Feb 08 07:42:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.