Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.6.4, 10.6.5, 10.6.7, 10.6.8, 10.6.9
-
None
Description
Since upgrading from 10.4 to 10.6 we are experiencing disk-space-problems on our replication-slave, because the innodb-temp-data-file "ibtmp1" was growing and growing up to the size of the original database.
MySQL allows limiting the max size of table-space with file_name:file_size[:autoextend[:max:max_file_size]]
(https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_temp_data_file_path) which works also for MariaDB, although not specified (https://mariadb.com/kb/en/innodb-system-variables/#innodb_temp_data_file_path).
However, the file grows up to the max-size although the temporary tables are not as big and then the replication stops:
Last error: Error 'Can't create table ... (errno: 135 "No more room in record file")' on query. Default database: '...'. Query: 'CREATE TEMPORARY TABLE `...` (
Note: Replication is statemend based (binlog_format = STATEMENT)
Workaround is to restart MariaDB once the temporary file reached the max size.
Attachments
Issue Links
- is caused by
-
MDEV-28183 Innodb-temp-data-file does not stop growing
- Closed
- is duplicated by
-
MDEV-28240 InnoDB Temporary Tablespace (ibtmp1) is continuously growing
- Closed
- relates to
-
MDEV-13013 InnoDB unnecessarily extends data files
- Closed