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

mysqld writes status information on HUP signal into innodb data file, breaking it

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.2.11
    • Fix Version/s: 10.2.12
    • Component/s: Server
    • Labels:
      None
    • Environment:
      FreeBSD 11.1-RELEASE-p4 amd64
      build from port databases/mariadb102-server

      Description

      Steps to reproduce on FreeBSD 11.1 amd64 box

      cd /usr/ports/databases/maraidb102-server
      make install
      select only INNODB engine and GSSAPI_NONE
      service mysql-server onestart
      killall -HUP mysqld
      head /var/db/mysql/ibdata1
      

      You will see a "Status information" here, instead of error_log file. It breaks database completely, mysqld will hung or crash in seconds depending on load

      On production server also error_log file will be flooded with gigs of binary data which I think are actual data should be written into ibdata1

      10.2.10 is not affected, 10.2.11 on Ubuntu 16.04 from official repo also isn't affected

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              serg Sergei Golubchik
              Reporter:
              hempalex Alexander Mikhailov
              Votes:
              0 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.