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

MariaDB 10.3 refuses InnoDB crash-upgrade from MariaDB 10.2

Details

    Description

      While the redo log format was changed in MariaDB 10.3.2 and 10.3.3 due to MDEV-12288 and MDEV-11369, it should be technically possible to upgrade from a crashed MariaDB 10.2 instance.

      On a related note, it should be possible for Mariabackup 10.3 to create a backup from a running MariaDB Server 10.2.

      Currently, both these are refused due to redo log format tag mismatch. We should remove the refusal and test the upgrade.

      The format tag will still serve its main purpose: preventing an older version of MariaDB from starting up from newer InnoDB files. Even that one we could theoretically relax if desired, in a separate issue: allow 10.2 to start up on files left behind by a clean shutdown of 10.3.

      Attachments

        Issue Links

          Activity

            marko Marko Mäkelä created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 84699 ] MariaDB v4 [ 153498 ]

            People

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