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

Replication stops because too big innodb-temp-data-file

    XMLWordPrintable

Details

    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

          Activity

            People

              thiru Thirunarayanan Balathandayuthapani
              alex2 Alex
              Votes:
              1 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.