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

Upgrade tests for InnoDB undo log

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • Tests
    • None

    Description

      Marko wrote:

      We'd need that for MDEV-12288. I manually tested for one (the default) innodb_page_size (I think this change is not really dependent on it). I'd suggest this, similar to innodb.read_only_recovery:
      1. Start the old version (any, even 5.5) with --innodb-change-buffering=none and run quite a bit of DML
      2. Kill & restart with --innodb-force-recovery=3 (important, to preserve the undo logs!)
      3. Restart the new version with --innodb-read-only (this would refuse to start up if the change buffer is not empty), run some DML (say, CHECK TABLE on every InnoDB table)
      4. Restart the new version normally, and run some more DML workload and CHECK TABLE.

      we'd actually have needed it already for MDEV-12289 (which made the 10.2.6 undo log compatible with 10.1 or earlier)

      I’d appreciate such a test with bb-10.3-marko

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              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.