[MDEV-25867] main.trigger-trans failed in bb, Assertion `ticket->m_duration == MDL_EXPLICIT' failed in MDL_context::release_lock Created: 2021-06-07  Updated: 2021-06-18  Resolved: 2021-06-18

Status: Closed
Project: MariaDB Server
Component/s: Tests, Triggers
Affects Version/s: 10.5, 10.6
Fix Version/s: 10.5.11, 10.6.3

Type: Bug Priority: Critical
Reporter: Alice Sherepa Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-25738 Assertion `ticket->m_duration == MDL_... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-asan/builds/6113/steps/mtr_nm/logs/stdio (MDEV-25738)

main.trigger-trans 'innodb'              w4 [ fail ]
        Test ended at 2021-06-06 15:09:54
 
CURRENT_TEST: main.trigger-trans
mysqltest: At line 247: query 'CREATE TRIGGER tr16 AFTER UPDATE ON t1 FOR EACH ROW INSERT INTO t1 VALUES (1)' failed: <Unknown> (2013): Lost connection to server during query
 
The result from queries just before the failure was:
< snip >
INSERT INTO t3 (id) VALUES (NEW.id);
END//
START TRANSACTION;
UPDATE t1 SET val = val + 1;
connect  con2,localhost,root,,test,,;
SET SESSION innodb_lock_wait_timeout = 2;
UPDATE t1 SET val = val + 1;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
INSERT INTO t2 (id) VALUES (1);
disconnect con2;
connection default;
DROP TABLE t3, t2, t1;
#
# MDEV-25738 Assertion `ticket->m_duration == MDL_EXPLICIT' failed in
# void MDL_context::release_lock(MDL_ticket*)
#
CREATE TABLE t1 (id int(11)) ENGINE=InnoDB;
LOCK TABLES t1 WRITE;
SET max_statement_time= 0.001;
CREATE TRIGGER tr16 AFTER UPDATE ON t1 FOR EACH ROW INSERT INTO t1 VALUES (1);
 
More results from queries before failure can be found in /dev/shm/var/4/log/trigger-trans.log
 
 
Server [mysqld.1 - pid: 215409, winpid: 215409, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
mariadbd: /home/buildbot/buildbot/build/mariadb-10.6.2/sql/mdl.cc:2841: void MDL_context::release_lock(MDL_ticket*): Assertion `ticket->m_duration == MDL_EXPLICIT' failed.
210606 15:09:53 [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.6.2-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=153
thread_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63859 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x62b000126288
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 = 0x7f6a9f57acd0 thread_stack 0x100000
??:0(__interceptor_tcgetattr)[0x7f6aac5aed30]
mysys/stacktrace.c:212(my_print_stacktrace)[0x55f4904d3447]
sql/signal_handler.cc:225(handle_fatal_signal)[0x55f48ef7c831]
??:0(__restore_rt)[0x7f6aac3c53c0]
??:0(gsignal)[0x7f6aabeb118b]
??:0(abort)[0x7f6aabe90859]
/lib/x86_64-linux-gnu/libc.so.6(+0x25729)[0x7f6aabe90729]
??:0(__assert_fail)[0x7f6aabea1f36]
sql/mdl.cc:2843(MDL_context::release_lock(MDL_ticket*))[0x55f48ebcc1f9]
sql/sql_trigger.cc:730(mysql_create_or_drop_trigger(THD*, TABLE_LIST*, bool))[0x55f48ea1ac5c]
sql/sql_parse.cc:5805(mysql_execute_command(THD*))[0x55f48e75c6ec]
sql/sql_parse.cc:8016(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55f48e76aebd]
sql/sql_parse.cc:1899(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55f48e741043]
sql/sql_parse.cc:1406(do_command(THD*, bool))[0x55f48e73dd70]
sql/sql_connect.cc:1410(do_handle_one_connection(CONNECT*, bool))[0x55f48eba0017]
sql/sql_connect.cc:1314(handle_one_connection)[0x55f48eb9f979]
perfschema/pfs.cc:2203(pfs_spawn_thread)[0x55f48f8b09b7]
??:0(start_thread)[0x7f6aac3b9609]
??:0(clone)[0x7f6aabf8d293]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x62b00012d2a8): CREATE TRIGGER tr16 AFTER UPDATE ON t1 FOR EACH ROW INSERT INTO t1 VALUES (1)
 
Connection ID (thread ID): 337
Status: KILL_TIMEOUT
 
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
 
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /dev/shm/var/4/mysqld.1/data
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    0                    bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             31505                31505                processes 
Max open files            1024                 1024                 files     
Max locked memory         67108864             67108864             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       31505                31505                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: |/usr/share/apport/apport %p %s %c %d %P %E
 
----------SERVER LOG END-------------



 Comments   
Comment by Elena Stepanova [ 2021-06-07 ]

Latest 10.5 occasion as of now:
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/6565/steps/mtr_centos_mix/logs/stdio
(10.5 3c97097f11bf111b7b25378e0c05011849e57541, build of June 4th)

Comment by Marko Mäkelä [ 2021-06-16 ]

An attempted fix that would rely on a debug-only data member is available. This test is very frequently failing on 10.5 and 10.6, mostly debug, ASAN or MSAN builds.

I believe that the problems started with a merge that included a fix of MDEV-17749.

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