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

LP:1021737 - deadlock inside xtradb on DDL operation

        Details

        • Type: Bug
        • Status: Closed
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: None
        • Component/s: None
        • Labels:

          Description

          mysql  Ver 15.1 Distrib 5.5.25-MariaDB, for Linux (x86_64) using readline 5.1

          Id	User	Host	db	Command	Time	State	Info	Progress
711	root	127.0.0.1:52513	NULL	Query	270	executing	SHOW /*!50002 GLOBAL*/ STATUS	0.000
712	root	127.0.0.1:52514	NULL	Sleep	0		NULL	0.000
4843	root	localhost	NULL	Query	539	NULL	SHOW /*innotop*/ ENGINE INNODB STATUS	0.000
5514	root	localhost	egw_amnesty_be	Query	543	Opening tables	optimize table egw_amnesty_be.egw_sitemgr_pages_lang	0.000
5562	root	localhost	egw_apartment91_	Query	543	Opening tables	optimize table egw_apartment91_.egw_sitemgr_blocks	0.000
5565	root	localhost	egw_apd_egroupwa	Query	543	rename result table	optimize table egw_apd_egroupwa.egw_wiki_rate	0.000
5575	root	localhost	egw_aquisys	Query	543	Opening tables	optimize table egw_aquisys.egw_nextid	0.000
5581	root	localhost	egw_ara_egroupwa	Query	543	After create	optimize table egw_ara_egroupwa.egw_accounts	0.000
5586	root	localhost	egw_arbora_klett	Query	541	creating table	alter table egw_arbora_klett.egw_access_log engine=innodb	0.000
5587	root	localhost	NULL	Query	541	NULL	drop database `egw_arbora`	0.000
5639	observium	localhost	NULL	Query	488	executing	SHOW /*!50002 GLOBAL */ STATUS	0.000
5936	observium	localhost	NULL	Sleep	189		NULL	0.000
61

          The deadlock occurred during a migration job doing things in parallel restauring dababase myisam tables from dump
          Selecting from information_schema
          Alter some table to innobb
          Optimizing table

          At least tables 150 tables * 1000 schema

          Reproduce deadlock with in-house script

          cnf , error log and 2 stack traces in http://pastebin.com/xtQ6v6yJ

          Contact Ralf Becker <email address hidden> on top of skysql consulting

            Gliffy Diagrams

              Attachments

                Issue Links

                links to

                Web Link LP #1007268 - Server crashing after upgrade (semaphore wait)

                Web Link LP #1038225 - Failing assertion: mutex_own(&buf_pool->mutex) in buf0lru.c on ADD PRIMARY KEY

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  stephanevaroqui Stephane VAROQUI added a comment -

                  Re: deadlock inside xtradb on DDL operation
                  Code used to get the issue

                  http://pastebin.com/nVh0ZQD2

                  Looks similar to

                  https://bugs.launchpad.net/percona-server/+bug/1007268

                  Need to try to reproduce with

                  Show
                  stephanevaroqui Stephane VAROQUI added a comment - Re: deadlock inside xtradb on DDL operation Code used to get the issue http://pastebin.com/nVh0ZQD2 Looks similar to https://bugs.launchpad.net/percona-server/+bug/1007268 Need to try to reproduce with
                  Hide
                  Permalink
                  ratzpo Rasmus Johansson added a comment -

                  Launchpad bug id: 1021737

                  Show
                  ratzpo Rasmus Johansson added a comment - Launchpad bug id: 1021737
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  The related bug family in XtraDB seems to be fixed by now (LP:1007268, LP:1038225, LP:1040735), so we can presume this issue got fixed along with them until there is evidence of the opposite (it wasn't reproducible with the provided data before, there were missing pieces of information, so the exact scenario can't be checked).

                  Show
                  elenst Elena Stepanova added a comment - The related bug family in XtraDB seems to be fixed by now (LP:1007268, LP:1038225, LP:1040735), so we can presume this issue got fixed along with them until there is evidence of the opposite (it wasn't reproducible with the provided data before, there were missing pieces of information, so the exact scenario can't be checked).

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      stephanevaroqui Stephane VAROQUI
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: