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

provide mechanism to monitor the status of dynamic redo log resize operation

    XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Server

    Description

      Currently, after changing the value of innodb_log_file_size using SET GLOBAL command, we dont have any mechanism to monitor the status (verified in 10.11.7).

      When we retry the operation when the operation is in progress, we receive below error:
      ERROR 1221 (HY000): innodb_log_file_size change is already in progress

      Provide a mechanism similar to below to monitor the status of the resizing operation available in mysql

      https://dev.mysql.com/doc/refman/8.4/en/server-status-variables.html#statvar_Innodb_redo_log_capacity_resized

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-27812 Allow innodb_log_file_size to change without server restart

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34750 SET GLOBAL innodb_log_file_size is not crash safe

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

          Activity

            People

              Unassigned Unassigned
              vidyadhar.chelluru vidyadhar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.