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

ibdata1 file size growing in MariaDB

    XMLWordPrintable

Details

    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 duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32414 [mariadb-galera] There is one node in a 3-node cluster, ibdata1, with a large file

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is part of

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26445 innodb_undo_log_truncate is unnecessarily slow

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-14795 InnoDB system tablespace cannot be shrunk

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-19229 Allow innodb_undo_tablespaces to be changed after database creation

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26450 Corruption due to innodb_undo_log_truncate

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-27734 Set innodb_change_buffering=none by default

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28187 mariadb-backup doesn't utilise innodb-undo-log-directory (if specified as a relative path) during copy-back operation

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29593 Purge misses a chance to free not-yet-reused undo pages

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-29983 Deprecate innodb_file_per_table

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Task - A task that needs to be done. MDEV-29986 Set innodb_undo_tablespaces=3 by default

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13013 InnoDB unnecessarily extends data files

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15528 Avoid writing freed InnoDB pages

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27153 ibdata1 file Leaking ? (errno 135) - using innodb_undo_tablespaces

          • Major - Major loss of function.
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              marko Marko Mäkelä
              tarun Tarun
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.