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

Allow moving UNDO segments into separate UNDO tablespaces without total rebuild of the data directory from a logical backup

Details

    Description

      On servers with bursts of data changes the system table space tends to grow due to UNDO segments stored there and cannot be shrinked again. The current workaround is to take a logical backup, reinitialize the data directory with previously configuring separate UNDO tablespaces and reload the data from the mysqldump file. For large databases it should be possible to move UNDO segments out of the system table space without rebuilding the whole data directory. This process is unacceptable due the long downtimes caused by exporting and re-importing the data.
      In new installations UNDO tablespaces should be default.

      Attachments

        Issue Links

          Activity

            umoser Ulrich Moser (Inactive) created issue -
            umoser Ulrich Moser (Inactive) made changes -
            Field Original Value New Value
            Description On servers with bursts of data changes the system table space tends to grow due to UNDO segments stored there and cannot be shrinked again. The current workaround is to take a logical backup, reinitialize the data directory with previously configuring separate UNDO tablespaces and reload the data from the mysqldump file. For large databases DO segments could be moved out of the system table space without rebuilding the whole data directory. On servers with bursts of data changes the system table space tends to grow due to UNDO segments stored there and cannot be shrinked again. The current workaround is to take a logical backup, reinitialize the data directory with previously configuring separate UNDO tablespaces and reload the data from the mysqldump file. For large databases it should be possible to move UNDO segments out of the system table space without rebuilding the whole data directory.
            In new installations UNDO tablespaces should be default.
            umoser Ulrich Moser (Inactive) made changes -
            Description On servers with bursts of data changes the system table space tends to grow due to UNDO segments stored there and cannot be shrinked again. The current workaround is to take a logical backup, reinitialize the data directory with previously configuring separate UNDO tablespaces and reload the data from the mysqldump file. For large databases it should be possible to move UNDO segments out of the system table space without rebuilding the whole data directory.
            In new installations UNDO tablespaces should be default.
            On servers with bursts of data changes the system table space tends to grow due to UNDO segments stored there and cannot be shrinked again. The current workaround is to take a logical backup, reinitialize the data directory with previously configuring separate UNDO tablespaces and reload the data from the mysqldump file. For large databases it should be possible to move UNDO segments out of the system table space without rebuilding the whole data directory. This process is unacceptable due the long downtimes caused by exporting and re-importing the data.
            In new installations UNDO tablespaces should be default.
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 90262 ] MariaDB v4 [ 130929 ]
            marko Marko Mäkelä made changes -

            This was actually implemented in MDEV-19229 (and MDEV-14795).

            marko Marko Mäkelä added a comment - This was actually implemented in MDEV-19229 (and MDEV-14795 ).
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2024-04-03 09:37:48.0 2024-04-03 09:37:47.791
            marko Marko Mäkelä made changes -
            Fix Version/s 10.11.1 [ 28454 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]

            People

              Unassigned Unassigned
              umoser Ulrich Moser (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.