Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
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
- duplicates
-
-
- Closed
-
Activity
| 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. |
| 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. |
| Workflow | MariaDB v3 [ 90262 ] | MariaDB v4 [ 130929 ] |
| Link |
This issue duplicates |
| issue.field.resolutiondate | 2024-04-03 09:37:48.0 | 2024-04-03 09:37:47.791 |
| Fix Version/s | 10.11.1 [ 28454 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
This was actually implemented in
MDEV-19229(andMDEV-14795).