Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18826

[Draft] Server crashed in l_find / MDL_map::remove

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.4(EOL)
    • N/A
    • Locking
    • None

    Description

      It might well be a duplicate of MDEV-18784, but the stack trace is so different, I can't know for sure.

      10.4 47b7ca62

      #3  <signal handler called>
      #4  0x000055f386f2761c in l_find (head=0x7fe39c0a1710, cs=0x55f387aabb20 <my_charset_bin>, hashnr=1022819193, key=0x7fe39c0a1738 "\002test", keylen=17, cursor=0x7fe3cc1bd3d0, pins=0x55f3891d9780, 
      callback=0x0) at /home/vsts/src/mysys/lf_hash.c:112
      #5  0x000055f386f279d3 in l_delete (head=0x55f3891e16f8, cs=0x55f387aabb20 <my_charset_bin>, hashnr=1022819193, key=0x7fe39c0a1738 "\002test", keylen=17, pins=0x55f3891d9780) at /home/vsts/src/mys
      ys/lf_hash.c:231
      #6  0x000055f386f281b2 in lf_hash_delete (hash=0x55f387c734e0 <mdl_locks>, pins=0x55f3891d9780, key=0x7fe39c0a1738, keylen=17) at /home/vsts/src/mysys/lf_hash.c:454
      #7  0x000055f38657ed06 in MDL_map::remove (this=0x55f387c734e0 <mdl_locks>, pins=0x55f3891d9780, lock=0x7fe39c0a1730) at /home/vsts/src/sql/mdl.cc:885
      #8  0x000055f38658026f in MDL_lock::remove_ticket (this=0x7fe39c0a1730, pins=0x55f3891d9780, list=&MDL_lock::m_granted, ticket=0x7fe39c05f6b0) at /home/vsts/src/sql/mdl.cc:1813
      #9  0x000055f386582131 in MDL_context::release_lock (this=0x7fe39c000e30, duration=MDL_TRANSACTION, ticket=0x7fe39c05f6b0) at /home/vsts/src/sql/mdl.cc:2817
      #10 0x000055f386582307 in MDL_context::release_locks_stored_before (this=0x7fe39c000e30, duration=MDL_TRANSACTION, sentinel=0x0) at /home/vsts/src/sql/mdl.cc:2867
      #11 0x000055f386582856 in MDL_context::release_transactional_locks (this=0x7fe39c000e30) at /home/vsts/src/sql/mdl.cc:3040
      #12 0x000055f38640d83d in mysql_execute_command (thd=0x7fe39c000d10) at /home/vsts/src/sql/sql_parse.cc:6463
      #13 0x000055f3864124b1 in mysql_parse (thd=0x7fe39c000d10, rawbuf=0x7fe39c031c78 "/* GenTest::Transform::ExecuteAsCTE */  INSERT testdb_S.t1_temp2_N WITH cte1 AS ( SELECT * FROM test.table0_int /*
       QNO 2822 CON_ID 16 */ ) SELECT * FROM cte1  /* TRANSFORM_OUTCOME_UNORDERED_MATCH */ /"..., length=223, parser_state=0x7fe3cc1be1d0, is_com_multi=false, is_next_command=false) at /home/vsts/src/sq
      l/sql_parse.cc:8157
      #14 0x000055f3863fd84e in dispatch_command (command=COM_QUERY, thd=0x7fe39c000d10, packet=0x7fe39c00a971 "/* GenTest::Transform::ExecuteAsCTE */  INSERT testdb_S.t1_temp2_N WITH cte1 AS ( SELECT *
       FROM test.table0_int /* QNO 2822 CON_ID 16 */ ) SELECT * FROM cte1  /* TRANSFORM_OUTCOME_UNORDERED_MATCH */ /"..., packet_length=223, is_com_multi=false, is_next_command=false) at /home/vsts/src/
      sql/sql_parse.cc:1829
      #15 0x000055f3863fbfd0 in do_command (thd=0x7fe39c000d10) at /home/vsts/src/sql/sql_parse.cc:1358
      #16 0x000055f386575785 in do_handle_one_connection (connect=0x55f38922bf40) at /home/vsts/src/sql/sql_connect.cc:1399
      #17 0x000055f3865754c3 in handle_one_connection (arg=0x55f38922bf40) at /home/vsts/src/sql/sql_connect.cc:1302
      #18 0x00007fe3ce48f6ba in start_thread (arg=0x7fe3cc1bf700) at pthread_create.c:333
      #19 0x00007fe3cd71441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
      

      The failure happened on the attached test case repro.test.reproducible.140, however I can't reproduce it so far by re-running it.

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.