Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 10.2.12, 10.2.13, 10.3.5
-
Fix Version/s: 10.2.15
-
Component/s: Galera
-
Labels:None
Description
It just takes a two(with more is the same) nodes Galera cluster with wsrep_slave_threads>1 on the Slave node(s).
On the Master node import the sql files in sequence and you'll get the crash with error log full of messages of the type:
2018-02-08 11:41:04 140048415356672 [Note] InnoDB: SQL1: DELETE FROM `CA9176ed2945`/)|Z�'
2018-02-08 11:41:04 140048415356672 [Note] InnoDB: SQL2:
2018-02-08 11:41:04 140048415356672 [ERROR] mysqld: Can't find record in 'CA9176ed2945'
2018-02-08 11:41:04 140048415356672 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table c17580.CA9176ed2945; Can't find record in 'CA9176ed2945', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log FIRST, end_log_pos 799009, Internal MariaDB error code: 1032
Attachments
Issue Links
- duplicates
-
MDEV-15611 Due to the failure of foreign key detection, Galera slave node killed himself.
-
- Closed
-