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

DELETE with CASCADE constraints takes long time and then crashes the instance with Signal 6

    XMLWordPrintable

Details

    Description

      Running DELETE on a table with a single ROW which causes a cascade constraint to trigger hangs for long time (about 20 minutes in the reported case) and then crashes the instance with:

      InnoDB: ###### Diagnostic info printed to the standard error stream
      2017-08-10 19:08:35 140481422710528 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server becau
      se it appears to be hung.
      170810 19:08:35 [ERROR] mysqld got signal 6 ;

      To reproduce:

      1) Import attached dump

      2) Execute:

      DELETE FROM BRc273a13dfda91b1add89;

      3) Wait ~20 minutes

      On 10.1 the same completes successfully in 15 seconds.

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              claudio.nanni Claudio Nanni
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 5h
                  5h

                  Git Integration

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