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

mysql_upgrade_service/mariadb-upgrade-service - avoid slow shutdown if not necessary

Details

    Description

      Slow shutdown (innodb_fast_shutdown=0) is currently used by mysql_upgrade_service, during upgrade, since that was advised previously. It can take a long time, so it is better be avoided.

      Tt is no more necessary . Instead. innodb_fast_shutdown=1 can be used.

      We would still restart and shutdown if service was not running prior to upgrade, to avoid crash recovery in the new version.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23755 safety for upgrades (innodb) and packaging

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25793 Update upgrading documentation

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            wlad Vladislav Vaintroub created issue -
            wlad Vladislav Vaintroub made changes -
            Field Original Value New Value
            wlad Vladislav Vaintroub made changes -
            wlad Vladislav Vaintroub made changes -
            Issue Type Task [ 3 ] Bug [ 1 ]
            wlad Vladislav Vaintroub made changes -
            Description Slow shutdown (innodb_fast_shutdown=0) is currently used by mysql_upgrade_service, during upgrade, since that was advised previously. It can take a long time, so it is better be avoided.

            For upgrading from MariaDB 10.3+, it is no more necessary . Instead. innodb_fast_shutdown=3 can be used.
             .             		Slow shutdown (innodb_fast_shutdown=0) is currently used by mysql_upgrade_service, during upgrade, since that was advised previously. It can take a long time, so it is better be avoided.

            Tt is no more necessary . Instead. innodb_fast_shutdown=1 can be used.
             .
            wlad Vladislav Vaintroub made changes -
            Description Slow shutdown (innodb_fast_shutdown=0) is currently used by mysql_upgrade_service, during upgrade, since that was advised previously. It can take a long time, so it is better be avoided.

            Tt is no more necessary . Instead. innodb_fast_shutdown=1 can be used.
             .             		Slow shutdown (innodb_fast_shutdown=0) is currently used by mysql_upgrade_service, during upgrade, since that was advised previously. It can take a long time, so it is better be avoided.

            Tt is no more necessary . Instead. innodb_fast_shutdown=1 can be used.

            We would still restart and shutdown if service was not running prior to upgrade, to avoid crash recovery in the new version.
            wlad Vladislav Vaintroub made changes -
            Fix Version/s 10.3.32 [ 26029 ]
            Fix Version/s 10.4.22 [ 26031 ]
            Fix Version/s 10.5.13 [ 26026 ]
            Fix Version/s 10.6.5 [ 26034 ]
            Fix Version/s 10.4 [ 22408 ]
            Fix Version/s 10.5 [ 23123 ]
            Fix Version/s 10.6 [ 24028 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 125734 ] MariaDB v4 [ 159727 ]

            People

              wlad Vladislav Vaintroub
              wlad Vladislav Vaintroub
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.