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

InnoDB: MySQL is trying to drop database…open handles to table …`#sql-ib1148`

Details

    Description

      Immediately after the push of MDEV-16678 into 10.5, we got the following failure on one platform:

      10.5 adb117cf6901a0e0da7577267be1209359892207

      innodb.foreign_key 'innodb'              w1 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2019-12-10 21:04:58
      line
      2019-12-10 21:04:53 3 [Warning] InnoDB: MySQL is trying to drop database `best`.`` though there are still open handles to table `best`.`#sql-ib1148`.
      ^ Found warnings in /dev/shm/var/1/log/mysqld.1.err
      

      http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/3140/steps/mtr/logs/stdio

      I am unable to repeat the failure. I believe that this could have been caused by the second commit of MDEV-16678.

      I believe that this would be best addressed by MDEV-8069 where the to-be-dropped tables would be moved into a separate directory.

      Attachments

        Issue Links

          Activity

            wlad Vladislav Vaintroub added a comment - - edited

            http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/16760/steps/test/logs/stdio

            Test ended at 2020-04-07 14:53:19
            line
            2020-04-07 14:53:13 3 [Warning] InnoDB: MySQL is trying to drop database `best`.`` though there are still open handles to table `best`.`#sql-ib899`.

            ^ Found warnings in D:/win32-debug/build/mysql-test/var/3/log/mysqld.1.err
            ok

            • saving 'D:/win32-debug/build/mysql-test/var/3/log/innodb.foreign_key-innodb/' to 'D:/win32-debug/build/mysql-test/var/log/innodb.foreign_key-innodb/'
            wlad Vladislav Vaintroub added a comment - - edited http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/16760/steps/test/logs/stdio Test ended at 2020-04-07 14:53:19 line 2020-04-07 14:53:13 3 [Warning] InnoDB: MySQL is trying to drop database `best`.`` though there are still open handles to table `best`.`#sql-ib899`. ^ Found warnings in D:/win32-debug/build/mysql-test/var/3/log/mysqld.1.err ok saving 'D:/win32-debug/build/mysql-test/var/3/log/innodb.foreign_key-innodb/' to 'D:/win32-debug/build/mysql-test/var/log/innodb.foreign_key-innodb/'

            The root cause of this is the background DROP TABLE queue, which cannot be removed before MDEV-21602 and MDEV-21175 have been addressed.

            marko Marko Mäkelä added a comment - The root cause of this is the background DROP TABLE queue, which cannot be removed before MDEV-21602 and MDEV-21175 have been addressed.
            midenok Aleksey Midenkov added a comment - http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-amd64/builds/21597/steps/mtr/logs/stdio

            Because we addressed MDEV-8069 with a much simpler change (relying on delete-on-close semantics), it did not fix this bug:

            10.5 c9f262ee0d256368cab4fdb894fd31d5fb669680

            innodb_fts.innodb_fts_misc 'innodb'      w2 [ fail ]  Found warnings/errors in server log file!
                    Test ended at 2020-06-11 16:35:47
            line
            2020-06-11 16:35:44 3 [Warning] InnoDB: MySQL is trying to drop database `benu database`.`` though there are still open handles to table `benu database`.`#sql-ib1795`.
            ^ Found warnings in /dev/shm/10.5/mysql-test/var/2/log/mysqld.1.err
            ok
            

            marko Marko Mäkelä added a comment - Because we addressed MDEV-8069 with a much simpler change (relying on delete-on-close semantics), it did not fix this bug: 10.5 c9f262ee0d256368cab4fdb894fd31d5fb669680 innodb_fts.innodb_fts_misc 'innodb' w2 [ fail ] Found warnings/errors in server log file! Test ended at 2020-06-11 16:35:47 line 2020-06-11 16:35:44 3 [Warning] InnoDB: MySQL is trying to drop database `benu database`.`` though there are still open handles to table `benu database`.`#sql-ib1795`. ^ Found warnings in /dev/shm/10.5/mysql-test/var/2/log/mysqld.1.err ok
            alice Alice Sherepa added a comment - http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/25074/steps/mtr_ps/logs/stdio
            alice Alice Sherepa added a comment - 10.5 http://buildbot.askmonty.org/buildbot/builders/kvm-deb-stretch-x86/builds/8834/steps/mtr/logs/stdio

            In MariaDB Server 10.6.2, this was fixed by MDEV-25506 part 3, by removing the "background DROP TABLE queue" hack. I do not think that this is fixable in earlier versions.

            marko Marko Mäkelä added a comment - In MariaDB Server 10.6.2, this was fixed by MDEV-25506 part 3, by removing the "background DROP TABLE queue" hack. I do not think that this is fixable in earlier versions.

            People

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