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

Crash whilst deleting row

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.1.36
    • N/A
    • Galera cluster, 3 nodes. Ubuntu 14.04.
      AWS EC2. Each node in same region, but different availability zone.

    Description

      Server crashed during normal operation. All writes to the Galera cluster, would have been directed at this one node.

      Full stack dump attached - but seemingly relevant part:

      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(+0x80f510)[0x7f911133e510]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0xff)[0x7f91110ffccf]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x112c)[0x7f91112206cc]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3bdb)[0x7f9110f693cb]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x321)[0x7f9110f6ee91]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(+0x4407bd)[0x7f9110f6f7bd]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1f9a)[0x7f9110f7211a]
      Nov  9 13:42:53 ip-10-38-166-188 mysqld: /usr/sbin/mysqld(_Z10do_commandP3THD+0x177)[0x7f9110f73017]
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              brendon Brendon Abbott
              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.