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

ALTER TABLE ... IMPORT/DISCARD TABLESPACE under LOCK TABLES doesn't acquire X metadata lock

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.0.17, 10.1.3
    • 10.1.5
    • Locking
    • None

    Description

      This problem was fixed along with MySQL WL#6671 "Improve scalability by not using thr_lock.c locks for InnoDB tables".

      Due to coding mistake thr_lock.c lock was necessary to isolate ALTER TABLE
      IMPORT/DISCARD TABLESPACE under LOCK TABLES from concurrent I_S queries/
      open HANDLERs.

      Change ALTER TABLE IMPORT/DISCARD TABLESPACE code to acquire X
      lock on table being imported/discarded even under lock tables.

      Attachments

        Issue Links

          is part of

          Task - A task that needs to be done. MDEV-7660 MySQL WL#6671 "Improve scalability by not using thr_lock.c locks for InnoDB tables"

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              serg Sergei Golubchik
              svoj Sergey Vojtovich
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.