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

Error messages upon refusal to crash-upgrade can be misleading

    XMLWordPrintable

Details

    Description

      When current 10.3 server attempts to crash-upgrade from current 10.1, e.g. 10.1.26, it says

      10.3 e1051590b61b455

      		 
      2017-08-31  4:13:38 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2.
      		 
      2017-08-31  4:13:38 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2218] with error Generic error

      which kind of implies that if redo log was created after 10.2.2, it would have been supported.

      However, upon crash-upgrade from the current 10.2 (e.g. 10.2.8) it says

      10.3 e1051590b61b455

      		 
      2017-08-31  2:37:53 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.2.8.
      		 
      2017-08-31  2:37:53 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2218] with error Generic error

      It's not critical, but maybe some clean-up is due there.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14848 MariaDB 10.3 refuses InnoDB crash-upgrade from MariaDB 10.2

          • Major - Major loss of function.
          • Closed

          Activity

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              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.