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

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2.11
    • 10.2.12
    • Server
    • None
    • 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

            This is most probably the same bug as MDEV-14488, which was fixed in MDEV-14337. And will be released in 10.2.12

            serg Sergei Golubchik added a comment - This is most probably the same bug as MDEV-14488 , which was fixed in MDEV-14337 . And will be released in 10.2.12

            Sergei, could you please give me a link to github commit for this patch?
            I can't find anything for MDEV-14337

            hempalex Alexander Mikhailov added a comment - Sergei, could you please give me a link to github commit for this patch? I can't find anything for MDEV-14337
            hempalex Alexander Mikhailov added a comment - Sorry, I found it https://github.com/mariadb/server/commit/36f84744031430747d27bfb2087c7ae51019a70a I confirm, it solves the problem.

            Thanks, closing.

            serg Sergei Golubchik added a comment - Thanks, closing.

            your current GA version has a huge bug that can easily cause data corruption... don't you think you should pull this version from the download page??

            jnicol Jonathan Nicol added a comment - your current GA version has a huge bug that can easily cause data corruption... don't you think you should pull this version from the download page??

            The problem unfortunately seems to have existed since MariaDB 10.2.4 already, so just pulling the latest version wouldn't have solved that much ...

            hholzgra Hartmut Holzgraefe added a comment - The problem unfortunately seems to have existed since MariaDB 10.2.4 already, so just pulling the latest version wouldn't have solved that much ...

            People

              serg Sergei Golubchik
              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.