[MDEV-18132] Lock conflict on Galera replica node causes node failure (duplicate key) Created: 2019-01-04  Updated: 2019-06-17  Resolved: 2019-06-17

Status: Closed
Project: MariaDB Server
Component/s: Galera, Locking, Replication
Affects Version/s: 10.1.37
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Guillaume Lefranc Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Debian 8.x



 Description   

Create Table: CREATE TABLE `service_uniqueid_4673_0_0_md5` (
  `id` int(10) unsigned DEFAULT NULL,
  `site_id` int(10) unsigned DEFAULT NULL,
  `md5` varchar(32) DEFAULT NULL,
  `hash` varchar(2000) DEFAULT NULL,
  UNIQUE KEY `md5` (`md5`,`site_id`),
  KEY `site_id` (`site_id`),
  KEY `id` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 4  trx id 226595099 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 1397 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 4  trx id 226595099 lock_mode X locks rec but not gap lock hold time 0 wait time before 
grant 0 
InnoDB: error in sec index entry update in
InnoDB: index `md5` of table `idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 32; hex 3336373630363663313038656331643230376131313263623230633166393537; asc 3676066c108ec1d207a112cb20c1f957;;
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d5200529; asc      );;
 
InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 333637356337373266323564613531323637336130333963333230356234; asc 3675c772f25da512673a039c3205b4; (total 32 bytes);
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d51fad78; asc      x;;
 
TRANSACTION 226595100, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
3 lock struct(s), heap size 1184, 2 row lock(s), undo log entries 1
MySQL thread id 12, OS thread handle 0x7ff271bc7b00, query id 10630959 Update_rows_log_event::ha_update_row(66718355)
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2018-12-21 21:02:01 140679266687744 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '3676066c108ec1d207a112cb20c1f957-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:01 140679266990848 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '6cc59935a8d338276698360fb6b04541-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 495, Internal MariaDB error code: 1062
2018-12-21 21:02:01 140679266687744 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718359
2018-12-21 21:02:01 140679266990848 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718355
2018-12-21 21:02:01 140679266990848 [Warning] WSREP: Failed to apply app buffer: seqno: 66718355, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
2018-12-21 21:02:01 140679266687744 [Warning] WSREP: Failed to apply app buffer: seqno: 66718359, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
2018-12-21 21:02:01 140679266687744 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '3676066c108ec1d207a112cb20c1f957-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:01 140679266687744 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718359
2018-12-21 21:02:01 140679266687744 [Warning] WSREP: Failed to apply app buffer: seqno: 66718359, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 3th time
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 2  trx id 226595125 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 235 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 2  trx id 226595125 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
2018-12-21 21:02:03 140679265475328 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '6321b481599e0b3eb48de4d6311aa17b-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:03 140679265475328 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718374
2018-12-21 21:02:03 140679265475328 [Warning] WSREP: Failed to apply app buffer: seqno: 66718374, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
2018-12-21 21:02:03 140679265475328 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '6321b481599e0b3eb48de4d6311aa17b-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:03 140679265475328 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718374
2018-12-21 21:02:03 140679265475328 [Warning] WSREP: Failed to apply app buffer: seqno: 66718374, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 3th time
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 2  trx id 226595146 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595146 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595145 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595146 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595146 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
InnoDB: error in sec index entry update in
InnoDB: index `md5` of table `idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 32; hex 663135353332633933636335303332366635303164316366352018-12-21 21:02:04 140679332498176 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry 'f15532c93cc50326f501d1cf5c56be5d-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
63353662InnoDB: error in sec index entry del undo in
InnoDB: index 653564; asc f15532c93cc50326f501d1cf5c56be5d;;
2018-12-21 21:02:04 140679332498176 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718386
 1: len 4; hex 0007`id` of table 3b11; asc   ; ;;
 2: len 6; hex 0006d5219afb; asc    !  ;;
 
InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 663135346531626632636531666635396531353237336234356637306232; asc f154e1bf2ce1ff59e15273b45f70b2; (total 32 bytes);
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d52147cd; asc    !2018-12-21 21:02:04 140679332498176 [Warning] WSREP: Failed to apply app buffer: seqno: 66718386, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
G ;;
 
`idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 2 fields;
 0: len 4; hex 000262af; asc   b ;;
 1: len 6; hex 0006d5219afb; asc    !  ;;
 
InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 4; hex 000262ae; asc   b ;;
 1: len 6; hex 0006d520f9ac; asc       ;;
 
TRANSACTION 226595147, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
3 lock struct(s), heap size 1184, 2 row lock(s), undo log entries 1
MySQL thread id 8, OS thread handle 0x7ff271a9fb00, query id 10631039 Update_rows_log_event::ha_update_row(66718382)
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
TRANSACTION 226595145, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
ROLLING BACK 4 lock struct(s), heap size 1184, 3 row lock(s)
MySQL thread id 17, OS thread handle 0x7ff271a55b00, query id 10631037 Update_rows_log_event::ha_update_row(66718384)
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2018-12-21 21:02:04 140679265475328 [Warning] InnoDB: record in index id was not found on rollback, trying to insert
InnoDB: error in sec index entry update in
InnoDB: index `md5` of table `idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 32; hex 6131323633363136InnoDB: error in sec index entry del undo in
InnoDB: index `md5` of table 2018-12-21 21:02:04 140679265475328 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry 'a1263616901c95c9332c6fdc9eb96c6c-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
`idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 32; hex 6631353533326339336363353033323666353031643163663563353662653564; asc f1393031633935633933333255633666642018-12-21 21:02:04 140679265475328 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718384
633965623936633663; asc a126361632901c95c9c9332c63cc5032fdc96f501deb1c96c2018-12-21 21:02:04 140679265475328 [Warning] WSREP: Failed to apply app buffer: seqno: 66718384, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
6c;;
 1:f5 len 4; hex 00073b11BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table ; asc   ; ;;
 2: len 6; hex 0006d5219afb; asc    ! c5`idservices`.`service_uniqueid_4673_0_0_md5` ;;
6b trx table locks 1 total table locks 3 
InnoDB: record e trx id 226595149PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 615d; lock_mode X3132 locks rec but not gap;35656366 lock hold time 0 wait time before grant 0 
3834
 1: len 4; hex 00073b11; asc  BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table 3836 `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 22659514961613139; lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
376264643230386531336533353939; asc a125 InnoDB: error in sec index entry update in
InnoDB: index `md5` of table ecf8486aa197bdd208e13e;;
3`idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 32; hex 3639383661663937373731646462306262386137363766643263383232323832; asc 599; (total 32 bytes);
 1: len 4; hex 00073b11; asc  2: len 6; hex 0006d5219afb; asc 6  ; ;98;
 2: len 6; hex 0006d5 6af209649; asc   !977     I  ;;71dd;
 
;TRANSACTION 226595149, ACTIVE 0 sec updating or deleting
 
 
InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 66313534653162663263653166663539653135mysql tables in use 1, locked 1
4 lock struct(s), heap size 1184, 2 row lock(s), undo log entries 1b0bb
8a767MySQL thread id 10, OS thread handle 0x7ff275a40b00, query id 10631040 Update_rows_log_event::ha_update_row(66718386)
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
3237336234356637306232; asc f154e1bf2ce1ff59e15273b45f70b2; (total 32 bytes);
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d52147cd; asc    !G ;;
 
fd2TRANSACTION 226595147, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
ROLLING BACK 5 lock struct(s), heap size 1184, 3 row lock(s)
cMySQL thread id 8, OS thread handle 0x7ff271a9fb00, query id 10631039 Update_rows_log_event::ha_update_row(66718382)
82
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2282;;
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d5219afb; asc    !  ;;
 
InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 363938363466636434393337626337393334656633363731643135393430; asc 69864fcd4937bc7934ef3671d15940; (total 32 bytes);
 1: len 4; hex 00073b11; asc   ; ;;
 2: len 6; hex 0006d5210317; asc    !  ;;
 
2018-12-21 21:02:04 140679265778432 [Warning] InnoDB: record in index md5 was not found on rollback, trying to insert
TRANSACTION 226595151, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
3 lock struct(s), heap size 1184, 2 row lock(s), undo log entries 1
MySQL thread id 17, OS thread handle 0x7ff271a55b00, query id 10631041 Update_rows_log_event::ha_update_row(66718384)
2018-12-21 21:02:04 140679265778432 [Warning] InnoDB: record in index md5 was not found on rollback, and a duplicate exists
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: error in sec index entry del undo in
InnoDB: index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5`
InnoDB: tuple DATA TUPLE: 2 fields;
 0: len 4; hex 000262b1; asc   b ;;
 1: len 6; hex 0006d5219afb; asc    !  ;;
 
InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 32
 0: len 4; hex 000262af; asc   b ;;2018-12-21 21:02:04 140679332498176 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry 'f15532c93cc50326f501d1cf5c56be5d-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
 
 1: len 6; hex 0006d5212018-12-21 21:02:04 140679332498176 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718386
9afb; asc    !  ;;
 
TRANSACTION 226595147, ACTIVE 0 sec updating or deleting
mysql tables in use 1, locked 1
ROLLING BACK 5 lock struct(s), heap size 1184, 3 row lock(s)
MySQL thread id 8, OS thread handle 0x7ff271a9fb00, query id 10631039 Update_rows_log_event::ha_update_row(66718382)
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2018-12-21 21:02:04 140679265778432 [Warning] InnoDB: record in index id was not found on rollback, trying to insert
2018-12-21 21:02:04 140679332498176 [Warning] WSREP: Failed to apply app buffer: seqno: 66718386, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 3th time
2018-12-21 21:02:04 140679265475328 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry 'a1263616901c95c9332c6fdc9eb96c6c-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:04 140679265778432 [ERROR] Slave SQL: Could not execute Update_rows_v1 event on table idservices.service_uniqueid_4673_0_0_md5; Duplicate entry '6986af97771ddb0bb8a767fd2c822282-473873' for key 'md5', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log FIRST, end_log_pos 239, Internal MariaDB error code: 1062
2018-12-21 21:02:04 140679265475328 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718384
2018-12-21 21:02:04 140679265778432 [Warning] WSREP: RBR event 2 Update_rows_v1 apply warning: 121, 66718382
2018-12-21 21:02:04 140679265475328 [Warning] WSREP: Failed to apply app buffer: seqno: 66718384, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 3th time
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table 2018-12-21 21:02:04 140679265778432 [Warning] WSREP: Failed to apply app buffer: seqno: 66718382, status: 1
         at galera/src/trx_handle.cpp:apply():353
Retrying 2th time
`idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 2  trx id 226595153 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 2  trx id 226595153 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595153 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 20 n bits 1056 index `id` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595156 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595153 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
BF-BF X lock conflict,mode: 1027 supremum: 0
conflicts states: my 0 locked 0
RECORD LOCKS space id 57119 page no 626 n bits 240 index `GEN_CLUST_INDEX` of table `idservices`.`service_uniqueid_4673_0_0_md5` trx table locks 1 total table locks 3  trx id 226595156 lock_mode X locks rec but not gap lock hold time 0 wait time before grant 0 
2018-12-21 21:02:04 7ff275a40b00  InnoDB: Assertion failure in thread 140679332498176 in file row0ins.cc line 285
InnoDB: Failing assertion: *cursor->index->name == TEMP_INDEX_PREFIX
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
181221 21:02:04 [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.
 
Server version: 10.1.37-MariaDB-1~jessie
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=9
max_threads=8002
thread_count=21
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1050159555 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fe492812008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7ff275a3fe18 thread_stack 0x48400
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7ff2765572ae]
/usr/sbin/mysqld(handle_fatal_signal+0x2fd)[0x7ff27608b38d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7ff2756a8890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7ff273a06067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff273a07448]
/usr/sbin/mysqld(+0x7c182b)[0x7ff27629a82b]
/usr/sbin/mysqld(+0x7c3a32)[0x7ff27629ca32]
/usr/sbin/mysqld(+0x7ee7f4)[0x7ff2762c77f4]
/usr/sbin/mysqld(+0x7f316a)[0x7ff2762cc16a]
/usr/sbin/mysqld(+0x7d157c)[0x7ff2762aa57c]
/usr/sbin/mysqld(+0x71889b)[0x7ff2761f189b]
/usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x543)[0x7ff2760969b3]
/usr/sbin/mysqld(_ZN21Update_rows_log_event11do_exec_rowEP14rpl_group_info+0x30f)[0x7ff27615efef]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x379)[0x7ff276150b79]
/usr/sbin/mysqld(wsrep_apply_cb+0x427)[0x7ff276038297]
/usr/lib/galera/libgalera_smm.so(_ZNK6galera9TrxHandle5applyEPvPF15wsrep_cb_statusS1_PKvmjPK14wsrep_trx_metaERS6_+0xcc)[0x7ff26852f7cc]
/usr/lib/galera/libgalera_smm.so(+0x217a54)[0x7ff268576a54]
/usr/lib/galera/libgalera_smm.so(_ZN6galera13ReplicatorSMM9apply_trxEPvPNS_9TrxHandleE+0x15e)[0x7ff268579d7e]
/usr/lib/galera/libgalera_smm.so(_ZN6galera13ReplicatorSMM11process_trxEPvPNS_9TrxHandleE+0x136)[0x7ff26857d726]
/usr/lib/galera/libgalera_smm.so(_ZN6galera15GcsActionSource8dispatchEPvRK10gcs_actionRb+0x1d8)[0x7ff268553708]
/usr/lib/galera/libgalera_smm.so(_ZN6galera15GcsActionSource7processEPvRb+0x76)[0x7ff268554ea6]
/usr/lib/galera/libgalera_smm.so(_ZN6galera13ReplicatorSMM10async_recvEPv+0x83)[0x7ff26857dd73]
/usr/lib/galera/libgalera_smm.so(galera_recv+0x2b)[0x7ff26859250b]
/usr/sbin/mysqld(+0x560637)[0x7ff276039637]
/usr/sbin/mysqld(start_wsrep_THD+0x452)[0x7ff276028712]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7ff2756a1064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff273ab962d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): 
Connection ID (thread ID): 10
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off
 
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.



 Comments   
Comment by Jan Lindström (Inactive) [ 2019-05-20 ]

Can you provide your cluster configuration and full unedited error log?

Generated at Thu Feb 08 08:41:44 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.