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

Upgrade tests for InnoDB undo log

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

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13430 InnoDB upgrade from previous versions to 10.3 is not possible

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

          Task - A task that needs to be done. MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12289 Keep 128 persistent rollback segments for compatibility and performance

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13437 InnoDB fails to return error for XA COMMIT or XA ROLLBACK in read-only mode

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13438 Assertion `(&(&LOCK_log)->m_mutex)->count > 0 && pthread_equal(pthread_self(), (&(&LOCK_log)->m_mutex)->thread)' failed in MYSQL_BIN_LOG::open or Assertion `info.dry_run || total_ha_2pc>(ulong)opt_bin_log' failed in ha_recover

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13520 InnoDB attempts UPDATE with DB_TRX_ID=0 if innodb_force_recovery=3

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13475 InnoDB: Failing assertion: lsn == log_sys->lsn || srv_force_recovery == SRV_FORCE_NO_LOG_REDO

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13476 TRX_UNDO_PAGE_TYPE mismatch when writing undo log after upgrade

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13495 Crash in rollback of a recovered INSERT transaction after upgrade

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22257 Assertion `trx_id > 0 || (flags & BTR_KEEP_SYS_FLAG)' failed in btr_cur_optimistic_update | Assertion `id' failed in trx_write_trx_id

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Fix Version/s 10.2 [ 14601 ]
            Fix Version/s 10.3 [ 22126 ]
            elenst Elena Stepanova made changes -
            Description Marko wrote:
            {quote}
            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)
            {quote}             		Marko wrote:
            {quote}
            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
            {quote}
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            elenst Elena Stepanova made changes -
            Status In Progress [ 3 ] Stalled [ 10000 ]
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            marko Marko Mäkelä made changes -
            elenst Elena Stepanova made changes -
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            elenst Elena Stepanova made changes -
            Roel Roel Van de Paar made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 81590 ] MariaDB v4 [ 133300 ]

            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.