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

Make innodb_read_only shutdown more robust

    Details

      Description

      If InnoDB is started in innodb_read_only mode such that recovered incomplete transactions exist at startup (but the redo logs are clean), an assertion will fail at shutdown, because there would exist some non-prepared transactions.

      InnoDB: Failing assertion: UT_LIST_GET_LEN(trx_sys->rw_trx_list) == trx_sys->n_prepared_trx
      

      Repeating this bug requires two restarts after ensuring that some InnoDB redo log has been written, making some changes of an incomplete transaction durable:

      --let $restart_parameters= --innodb-force-recovery=3
      --source include/kill_and_restart_mysqld.inc
      --let $restart_parameters= --innodb-read-only
      --source include/restart_mysqld.inc
      --let $restart_parameters=
      --source include/restart_mysqld.inc
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marko Marko Mäkelä
                Reporter:
                marko Marko Mäkelä
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: