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

Optimization for dropping table

    XMLWordPrintable

Details

    Description

      When innodb_file_per_table=ON, each table has its only ibd file, user thread has to unlink refered ibd file when drop table is executed. as a result, it cost a lot of time when the ibd file is large and stall the whole system.

      For detail information, please refer to: https://github.com/MariaDB/server/pull/1021

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-32786 Support NBO for DROP TABLE in Galera

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8069 DROP or rebuild of a large table may lock up InnoDB

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

          Task - A task that needs to be done. MDEV-9459 Truncate table causes innodb stalls

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16796 TRUNCATE TABLE slowdown with innodb_file_per_table=ON

          • Major - Major loss of function.
          • Closed

          Activity

            People

              marko Marko Mäkelä
              musazhang musazhang
              Votes:
              2 Vote for this issue
              Watchers:
              8 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.