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

Implement binlog_space_limit

    XMLWordPrintable

Details

    • New Feature
    • Status: In Testing (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 11.4
    • None

    Description

      Original request:
      We have a 130GB database, replicated to a backup cluster, and the binlog files consume 400GB of storage for a single day, without any option to reduce that to something more reasonable!

      Implementation guidelines:

      • Add variable to limit max binlog space (max-binlog-total-space and/or binlog_space_limit)
      • Binlog size should be checked at during server start, binlog rotation, FLUSH LOGS, when writing to binary log or when max-binlog-total-size changes value.
      • Add option --slave-connections-needed-for-purge with 1 as default. This is the minimum number of slaves
        that needs to be connected for binary logs to be deleted.
      • Add status variable 'Binlog_disk_use' that shows current binary log space usage.

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              ccounotte COUNOTTE CEDRIC
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.