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

Server hangs when using --init-file which loads Spider and creates a Spider table

    XMLWordPrintable

    Details

      Description

      This issue is high priority as it affects Spider testing.

      # mysqld options required for replay:  --init-file=${PWD}/in.sql
      		 
       
      		 
      $ cat in.sql
      		 
      INSTALL PLUGIN spider SONAME 'ha_spider.so';
      		 
      USE test;
      		 
      CREATE TABLE t (c INT) ENGINE=SPIDER;

      Will make the server hang on startup. Attempted CLI connects will also hang. Removing either the INSTALL PLUGIN or the USE test from the testcase will make the server start correctly.

      Bug confirmed present in:
      MariaDB: 10.4.23 (dbg), 10.4.23 (opt), 10.5.14 (dbg), 10.5.14 (opt), 10.6.6 (dbg), 10.6.6 (opt), 10.7.2 (dbg), 10.7.2 (opt), 10.8.0 (dbg), 10.8.0 (opt)

      Bug (or feature/syntax) confirmed not present in:
      MariaDB: 10.2.42 (dbg), 10.2.42 (opt), 10.3.33 (dbg), 10.3.33 (opt)

        Attachments

          Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27095 spiders' background initialization causes conflicts with mysql-upgrade (and general improvements)

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-27253 Reorganize Spider plugin variables regarding table/index stats

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27575 SIGSEGV in intern_plugin_lock on SHUTDOWN when setting Spider as default storage engine (temporary or global)

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28218 Spider: thread hang/deadlock as result of INSTALL PLUGIN and DROP TABLE

          • Major - Major loss of function.
          • Open
          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20179 Server hangs on shutdown during installation of Spider

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19842 Crash while creating statistics for Spider table

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22979 "mysqld --bootstrap" / mysql_install_db hangs when Spider is installed

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27095 spiders' background initialization causes conflicts with mysql-upgrade (and general improvements)

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27103 mariadb-upgrade fails with 'System table spider_tables is different version' => Can't create database 'performance_schema'

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27614 SQL service crashes on some queries sent by SPIDER engine.

          • Major - Major loss of function.
          • In Progress

            Activity

              People

              Assignee:
              holyfoot Alexey Botchkov
              Reporter:
              Roel Roel Van de Paar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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