galera.galera_FK_duplicate_client_insert 'innodb' w2 [ retry-fail ]
|
Test ended at 2020-09-29 14:21:13
|
|
CURRENT_TEST: galera.galera_FK_duplicate_client_insert
|
mysqltest: At line 101: query 'commit' failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 0...
|
|
The result from queries just before the failure was:
|
< snip >
|
connection node_1_u;
|
commit;
|
connection node_1;
|
truncate user_session;
|
set debug_sync = reset;
|
connection node_1_u;
|
begin;
|
update user set j = j + 1 WHERE id > 0;
|
connection node_1_i;
|
set debug_sync='lock_wait_suspend_thread_enter SIGNAL ins_waiting WAIT_FOR cont_ins';
|
insert into user_session(id,fk1,fk2) values (2, 2, 2);
|
connection node_1;
|
set debug_sync='now WAIT_FOR ins_waiting';
|
connection node_2_i;
|
insert into user_session(id,fk1,fk2) values (2, 2, 3);
|
connection node_1;
|
set debug_sync='now SIGNAL cont_ins';
|
connection node_1_i;
|
connection node_1_u;
|
commit;
|
|
More results from queries before failure can be found in /dev/shm/var/2/log/galera_FK_duplicate_client_insert.log
|
|
|
Server [mysqld.1 - pid: 6884, winpid: 6884, exit: 256] failed during test run
|
Server log from this test:
|
----------SERVER LOG START-----------
|
2020-09-29 14:20:57 1 [ERROR] InnoDB: Conflicting lock on table: `test`.`user` index: PRIMARY that has lock
|
RECORD LOCKS space id 35 page no 3 n bits 72 index PRIMARY of table `test`.`user` trx id 369 lock mode S locks rec but not gap
|
Record lock, heap no 3 PHYSICAL RECORD: n_fields 4; compact format; info bits 0
|
0: len 4; hex 80000002; asc ;;
|
1: len 6; hex 000000000000; asc ;;
|
2: len 7; hex 80000000000000; asc ;;
|
3: len 4; hex 80000000; asc ;;
|
|
2020-09-29 14:20:57 1 [ERROR] InnoDB: WSREP state:
|
2020-09-29 14:20:57 1 [ERROR] WSREP: Thread BF trx_id: 372 thread: 1 seqno: 78 client_state: exec client_mode: high priority transaction_mode: replaying applier: 1 toi: 0 local: 0 query: update user set j = j + 1 WHERE id > 0�Bs_
|
2020-09-29 14:20:57 1 [ERROR] WSREP: Thread BF trx_id: 369 thread: 2 seqno: 77 client_state: exec client_mode: high priority transaction_mode: executing applier: 1 toi: 0 local: 0 query: insert into user_session(id,fk1,fk2) values (2, 2, 3)�Bs_
|
2020-09-29 14:20:57 0x7fbbf83b1700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.6/storage/innobase/lock/lock0lock.cc line 655
|
Could someone confirm if this:
MDEV-24892is the same crash?Are there any rough ideas when the fixed versions will get officially released? I know release estimates are hard.
Thanks for your time.
:edit: never mind, this is actually already released and already deployed in our environment (thanks to automatic CD), the question is still if these are the same crashes, but I will discuss that in the linked bug report.