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

Crashes after upgrade from 5.5.52 to 10.2.12

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.2.12, 10.2.14
    • N/A
    • None
    • Linux x86_64

    Description

      In two different environments, we have experienced periodic crashes after upgrading from 5.5.52 to 10.2.12. The first wave of investigation was covered in https://jira.mariadb.org/browse/MDEV-14915 but was written off as an upgrade procedure problem, since the crashes eventually stopped.

      But now in a new environment, we have experienced three identical crashes within the first 24 hours of the upgrade, all with the same blame as before:

      0x7fd2900b0700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/que/que0que.cc line 567

      We need a way to prevent these crashes before we proceed with upgrading the other ten servers in our environment.

      Attached is the error log detailing the upgrade at 2018-03-05 16:20, and the crashes at 180306 8:12:14 , 2018-03-06 09:59:37, and 180306 10:39:04

      Attachments

        Issue Links

          Activity

            @marko Due to the expense of the project overall, we were forced to temporarily unresource this project back in May. This is back on our radar for 2019. Please stand by.

            dvanhollen Doug Van Hollen added a comment - @marko Due to the expense of the project overall, we were forced to temporarily unresource this project back in May. This is back on our radar for 2019. Please stand by.

            dvanhollen, did you get back to the upgrade project?

            marko Marko Mäkelä added a comment - dvanhollen , did you get back to the upgrade project?

            @Marko We have abandoned the idea of an in-place upgrade and instead are focused on a cloud transition, which would circumvent this problem. I'm afraid we can't resource additional R&D at this time.

            dvanhollen Doug Van Hollen added a comment - @Marko We have abandoned the idea of an in-place upgrade and instead are focused on a cloud transition, which would circumvent this problem. I'm afraid we can't resource additional R&D at this time.

            The requested data was never provided. It is possible (but not certain) that this problem was addressed in MDEV-15507.

            marko Marko Mäkelä added a comment - The requested data was never provided. It is possible (but not certain) that this problem was addressed in MDEV-15507 .

            Another possibility is that this was fixed by MDEV-12023.

            marko Marko Mäkelä added a comment - Another possibility is that this was fixed by MDEV-12023 .

            People

              marko Marko Mäkelä
              dvanhollen Doug Van Hollen
              Votes:
              1 Vote for this issue
              Watchers:
              4 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.