Details
-
Task
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
Description
Now that MDEV-19229 allows the parameter innodb_undo_tablespaces to be increased from its current default value 0, we should enable multiple undo tablespaces by default. Likewise, we should set innodb_undo_log_truncate=ON by default, so that the space occupied by possible bursts of undo log records will be eventually reclaimed.
Edit: Based on some preliminary performance test results presented by axel, innodb_undo_log_truncate=ON seems to reduce throughput. That setting can be changed by SET GLOBAL while the server is running. The main thing here is to run the server with multiple tablespaces by default, so that it will be possible to truncate the undo tablespaces while the server is running.
Space that was occupied by undo logs in the system tablespace will not be reclaimed until MDEV-14795 has been implemented.
Attachments
Issue Links
- causes
-
MDEV-32974 Member fails to join due to old seqno in GTID
- Closed
- is blocked by
-
MDEV-19229 Allow innodb_undo_tablespaces to be changed after database creation
- Closed
-
MDEV-29999 innodb_undo_log_truncate=ON is not crash safe
- Closed
-
MDEV-30119 INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION.NAME is NULL for undo tablespaces
- Closed
-
MDEV-30122 mariabackup.skip_innodb crashes when innodb_undo_tablespaces > 0
- Closed
-
MDEV-30144 Incremental prepare fails when innodb_undo_tablespaces > 0
- Closed
-
MDEV-30157 Galera SST doesn't properly handle undo* files from innodb
- Closed
-
MDEV-30158 InnoDB fails to start ther server 10.11 when innodb_undo_tablespaces mismatch
- Closed
-
MDEV-30180 Server hang with innodb_undo_log_truncate=ON
- Closed
- is duplicated by
-
MDEV-31760 innodb_undo_tablespaces would be better default >= 2
- Closed
- relates to
-
MDEV-14795 InnoDB system tablespace cannot be shrunk
- Closed
-
MDEV-30179 mariabackup --backup fails with FATAL ERROR: ... failed to copy datafile.
- Closed
-
MDEV-30479 OPT_PAGE_CHECKSUM mismatch during recovery after innodb_undo_log_truncate=ON
- Closed
-
MDEV-35689 InnoDB system tables cannot be optimized or defragmented
- Confirmed
-
MDEV-21952 ibdata1 file size growing in MariaDB
- Closed
-
MDEV-32141 More fully document innodb_undo_tablespaces=3 by default
- Closed