Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.2.25
-
Component/s: Storage Engine - InnoDB
-
Labels:None
-
Environment:MariaDB Galera 3 Node DR
Description
We are using DATETIME Interval in most of our MariaDB Tables where we have automated Data Purging Process to delete data at Interval 1 DAY , INTERVAL 1 HOUR and we have Optimize Table script which runs once in day ( ALTER TABLE <table> ENGINE=InnoDB )
It is observed ibdata1 file in mysql folder has grown to 122 GB
Do we have Tuning options or Space recovery options that we can some have workaround on ibdata1 file ?
Attachments
Issue Links
- is part of
-
MDEV-26445 innodb_undo_log_truncate is unnecessarily slow
-
- Closed
-
- relates to
-
MDEV-19229 Allow innodb_undo_tablespaces to be changed after database creation
-
- In Progress
-
-
MDEV-26450 Corruption due to innodb_undo_log_truncate
-
- Closed
-
-
MDEV-27734 Set innodb_change_buffering=none by default
-
- Closed
-
-
MDEV-28187 mariadb-backup doesn't utilise innodb-undo-log-directory (if specified as a relative path) during copy-back operation
-
- Confirmed
-
-
MDEV-13013 InnoDB unnecessarily extends data files
-
- Stalled
-
-
MDEV-15528 Avoid writing freed InnoDB pages
-
- Closed
-
-
MDEV-27153 ibdata1 file Leaking ? (errno 135) - using innodb_undo_tablespaces
-
- Needs Feedback
-