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

mysql_upgrade crashes the server with REPAIR VIEW

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Blocker
        • Resolution: Fixed
        • Affects Version/s: 10.0.18, 5.5.43
        • Fix Version/s: 10.0.19, 5.5.44
        • Component/s: Admin statements, Views
        • Labels:
          None

          Description

          create table t1 (a blob);
create view v1 as select * from t1;
repair view v1;

            Gliffy Diagrams

              Attachments

                Issue Links

                duplicates

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8108 MariaDB 5.5.43 segfaults on startup

                • Major - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8117 REPAIR VIEW crashes thread

                • Major - Major loss of function.
                • Closed
                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-6916 Upgrade from MySQL to MariaDB breaks already created views

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  stephentenberg Stephen Tenberg added a comment -

                  This happened to me upon trying to upgrade to 10.0.18 on Ubuntu 14.04. I traced it to two views. (The rest of the views didn't trigger the crash). After dropping the two views I did a full mysql_upgrade --force and was able to start the server normally (and then add back the two simple views).

                  Show
                  stephentenberg Stephen Tenberg added a comment - This happened to me upon trying to upgrade to 10.0.18 on Ubuntu 14.04. I traced it to two views. (The rest of the views didn't trigger the crash). After dropping the two views I did a full mysql_upgrade --force and was able to start the server normally (and then add back the two simple views).
                  Hide
                  Permalink
                  michaeldg Michaël de groot added a comment -

                  I was able to work around this by dropping this view (MDEV-8117) and adding it again after running mysql_upgrade. There are over 100 views in the installation, fortunatelty only 1 caused issues.

                  Show
                  michaeldg Michaël de groot added a comment - I was able to work around this by dropping this view ( MDEV-8117 ) and adding it again after running mysql_upgrade. There are over 100 views in the installation, fortunatelty only 1 caused issues.
                  Hide
                  Permalink
                  azurit azurit added a comment - - edited

                  We were experiencing this crash even when upgrading from 5.5.42 to 5.5.43 on SEVERAL servers (it crashed during REPAIR query). I just read the warning that we shouldn't upgrade but we already did and it was crashing most of the time - what damage was done to our data? How should we repair it?

                  Show
                  azurit azurit added a comment - - edited We were experiencing this crash even when upgrading from 5.5.42 to 5.5.43 on SEVERAL servers (it crashed during REPAIR query). I just read the warning that we shouldn't upgrade but we already did and it was crashing most of the time - what damage was done to our data? How should we repair it?
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  No damage whatsoever. Just don't run mysql_upgrade when upgrading from 5.5.42 and you're fine.

                  Show
                  serg Sergei Golubchik added a comment - No damage whatsoever. Just don't run mysql_upgrade when upgrading from 5.5.42 and you're fine.
                  Hide
                  Permalink
                  azurit azurit added a comment -

                  As i said, we already did and it did crash on several servers during the upgrade process (5.5.42 -> 5.5.43). Does the upgrade script needs to be run again or next MariaDB version (5.5.44) will fix it automatically?

                  Show
                  azurit azurit added a comment - As i said, we already did and it did crash on several servers during the upgrade process (5.5.42 -> 5.5.43). Does the upgrade script needs to be run again or next MariaDB version (5.5.44) will fix it automatically?
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  Your tables and views are ok, there is nothing wrong with the data. The bug was in mysqld binary and when it'll be replaced with the next version the bug will go away.

                  Show
                  serg Sergei Golubchik added a comment - Your tables and views are ok, there is nothing wrong with the data. The bug was in mysqld binary and when it'll be replaced with the next version the bug will go away.

                    People

                    • Assignee:
                      serg Sergei Golubchik
                      Reporter:
                      serg Sergei Golubchik
                    • Votes:
                      1 Vote for this issue
                      Watchers:
                      8 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: